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) - ...
Risk signalsAdmin/system-level operation
Part of the Shrike Security server.
Free to start. No card required.
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.
{
"version": "1",
"default": "deny",
"tools": {
"get_threat_intel": {}
}
}See the full Shrike Security policy for all 12 tools.
These attack patterns abuse exactly the kind of access get_threat_intel gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
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.
Register the Shrike Security MCP server in PolicyLayer and add a rule for get_threat_intel: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Shrike Security. Nothing to install.
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 PolicyLayer 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 PolicyLayer 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). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Shrike Security tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.