Fetch a single MISP event by id, including its attributes (IOCs).
AI agents call misp_get_event to retrieve information from UltraProbe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from a MISP (Malware Information Sharing Platform) instance without modifying, deleting, or executing any operations. It is a straightforward read operation that queries event data. The blast radius of misuse is low—an agent could fetch sensitive threat intelligence, but cannot alter or delete records.
From the tool's definition Tool name is 'misp_get_event' and description states 'Fetch a single MISP event by id, including its attributes (IOCs)'. The verb 'Fetch' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
Fetch a single MISP event by id, including its attributes (IOCs). It is categorised as a Read tool in the UltraProbe MCP Server, which means it retrieves data without modifying state.
Register the UltraProbe 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 UltraProbe. 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 UltraProbe MCP server (ppcvote/misp-mcp-server). 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 →