AI agents call misp_get_event to retrieve information from Misp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
misp_get_event fetches and queries existing threat intelligence data without side effects. It enables investigations and correlation discovery as intended by the server's design. The most severe risk is information disclosure, which is inherent to a threat intelligence platform and typical of Read operations. No write, execute, destructive, or financial operations are performed.
From the tool's definition Tool retrieves 'full details of a specific MISP event including all attributes, objects, tags, and related events' — classic read operation with no modification or deletion.
Attacks that exploit this kind of access
Get full details of a specific MISP event including all attributes, objects, tags, and related events. It is categorised as a Read tool in the Misp MCP Server, which means it retrieves data without modifying state.
Register the Misp MCP server in PolicyLayer and add a rule for misp_get_event: 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 Misp. Nothing to install.
misp_get_event 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 misp_get_event 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 misp_get_event. 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.
misp_get_event is provided by the Misp MCP server (solomonneas/misp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →