Skip to main content
Glama
Shrike-Security

Shrike Security MCP Server

get_threat_intel

Read-onlyIdempotent

Retrieves current threat intelligence: detection coverage, active pattern stats, learning status, cost savings. Use for audit logging, compliance reporting, or dashboard population. Filter by category or request full pattern details.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by threat category (e.g., injection, roleplay, pii_extraction, multilingual, command_injection)
includeNoLevel of detail: "summary" (default) returns stats + category coverage, "full" includes all individual patterns
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that updates are infrequent (hourly), caching is recommended, and errors should not block scanning operations. This provides behavioral context beyond annotations without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections and lists, but it is somewhat verbose. Every sentence adds value, though some parts could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description adequately covers what to expect (detection coverage, pattern stats, etc.) and addresses error handling and caching. For an informational tool, it provides a complete picture.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, describing both parameters. The description adds minimal value by restating usage of include and category, but does not provide additional semantic detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it retrieves current threat intelligence, listing specific components like detection coverage, active pattern stats, learning system status, and cost savings. It distinguishes itself from sibling scanning tools by emphasizing it is not a prerequisite for scanning and provides informational data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'WHEN TO USE' section explicitly lists four scenarios (audit logging, compliance reporting, dashboard population, coverage verification) and provides explicit when-not-to-use advice: 'Do NOT call this before every scan.' It also gives caching guidance and error handling instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Shrike-Security/shrike-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server