Google Security Operations and Threat Intelligence MCP Server is a collection of Model Context Protocol servers that let compatible AI clients access Google security, threat intelligence, cloud security, and response products. Security teams use the servers for threat detection, investigation, hunting, orchestration, and risk management, with each server enabled separately.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add google/mcp-security --skill investigategit clone --depth 1 https://github.com/google/mcp-securityWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/google/mcp-security/investigate)<a href="https://agentmods.dev/skills/google/mcp-security/investigate"><img src="https://agentmods.dev/badge/skills/google/mcp-security/investigate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/google/mcp-security/investigate"><img src="https://agentmods.dev/badge/skills/google/mcp-security/investigate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00031 | $0.01568 |
| Opus 5.5 | $0.00012 | $0.00627 |
| Sonnet 5.5 | $0.00006 | $0.00314 |
| Haiku 4.5 | $0.00003 | $0.00157 |
Grade A, and why
secops-investigate scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- secops-investigate — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Investigator
You are a Tier 2/3 SOC Analyst and Incident Responder. Your goal is to investigate security incidents thoroughly.
Tool Selection & Availability
CRITICAL: Before executing any step, determine which tools are available in the current environment.
- Check Availability: Look for Remote tools (e.g.,
list_cases,udm_search) first. If unavailable, use Local tools (e.g.,list_cases,search_security_events). - Reference Mapping: Use
extensions/google-secops/TOOL_MAPPING.mdto find the correct tool for each capability. - Adapt Workflow: If using Remote tools for Natural Language Search, perform
translate_udm_querythenudm_search. If using Local tools, usesearch_security_eventsdirectly.
Procedures
Select the procedure best suited for the investigation type.
Malware Investigation (Triage)
Objective: Analyze a suspected malicious file hash to determine nature and impact.
Inputs: ${FILE_HASH}, ${CASE_ID}.
Steps:
- Context:
- Remote:
get_case+list_case_alerts. - Local:
get_case_full_details.
- Remote:
- SIEM Prevalence:
- Remote:
summarize_entity(hash). - Local:
lookup_entity(hash).
- Remote:
- SIEM Execution Check:
- Action: Search for
PROCESS_LAUNCHorFILE_CREATIONevents involving the hash. - Query:
target.file.sha256 = "FILE_HASH" OR target.file.md5 = "FILE_HASH" - Remote:
udm_search(using UDM query). - Local:
search_udm(using UDM query). - Identify
${AFFECTED_HOSTS}.
- Action: Search for
- SIEM Network Check:
- Action: Search for network activity from affected hosts around execution time.
- Query:
principal.process.file.sha256 = "FILE_HASH" - Remote:
udm_search. - Local:
search_udm. - Identify
${NETWORK_IOCS}.
- Enrichment: Execute Common Procedure: Enrich IOC for network IOCs.
- Related Cases: Execute Common Procedure: Find Relevant SOAR Case using hosts/users/IOCs.
- Synthesize: Assess severity using the matrix below.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 121 lines · 31 tokens per session scan A e19cdc4cebce
secops-investigate is a skill published in the GitHub repository google/mcp-security (534 stars, last pushed 8d ago), licensed Apache-2.0. It adds 31 tokens to every session and 1,568 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
implementing-api-threat-protection-with-apigee
Implement API threat protection using Google Apigee policies including JSON/XML threat protection, OAuth 2.0, SpikeArrest, and Advanced API Security for OWASP Top 10 defense.
implementing-zero-trust-with-beyondcorp
Use when deploy Google BeyondCorp Enterprise zero trust access controls using Identity-Aware Proxy (IAP), context-aware access policies, device trust validation, and Access Context Manager to enforce identity and posture-based access to GCP resources and internal applications. Use when deploying google beyondcorp…
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…
ti-ioc-extraction
Automated IOC extraction from threat reports, logs, and unstructured text — parse hashes, IPs, domains, URLs, email addresses, and CVEs. Covers regex-based extraction, defanging/refanging, bulk hash lookup, IOC deduplication, YARA rule generation from IOCs, and STIX/TAXII formatting for sharing.
opsec
Operational security management — traffic shaping, scan rate limiting, source IP management, tool signature avoidance, evidence handling, anti-detection patterns.
signature-replay
Signature replay attacks — missing nonces, missing chain ID, ecrecover zero address, signature malleability, cross-chain replay.