Retrieves current threat intelligence: detection coverage, active pattern stats, learning system status, and cost savings. WHEN TO USE: - Audit logging: record which patterns were active during a scan session - Compliance reporting: demonstrate scanner coverage to auditors (SOC 2, GDPR, HIPAA) -...
Admin/system-level operation
Part of the Shrike Security MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_threat_intel to retrieve information from Shrike Security without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_threat_intel only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_threat_intel:
rules:
- action: allowSee the full Shrike Security policy for all 12 tools.
Agents calling read-class tools like get_threat_intel have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Retrieves current threat intelligence: detection coverage, active pattern stats, learning system status, and cost savings. WHEN TO USE: - Audit logging: record which patterns were active during a scan session - Compliance reporting: demonstrate scanner coverage to auditors (SOC 2, GDPR, HIPAA) - Dashboard population: display threat statistics in admin interfaces - Coverage verification: confirm detection exists for a specific threat category Use include="full" for individual pattern details. Filter by category for targeted intel. Threat intelligence updates infrequently (hourly, not per-request). Cache results for the duration of your session or for up to 1 hour. Do NOT call this before every scan — it is an informational tool, not a prerequisite for scanning. Enterprise context: Provides the evidence trail that enterprise security and compliance teams require. ERROR HANDLING: If this tool returns an error, use cached results if available. Threat intel unavailability should NOT block scanning operations.. It is categorised as a Read tool in the Shrike Security MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_threat_intel. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Shrike Security MCP server.
get_threat_intel is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_threat_intel rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the Intercept policy for get_threat_intel. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_threat_intel is provided by the Shrike Security MCP server (shrike-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept