AI agents call misp_list_organisations 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.
This tool retrieves organization metadata from MISP without altering any data. It enables discovery of local and remote sharing partners, which is purely informational. The blast radius of misuse is minimal—an attacker could discover organizational relationships but cannot modify configurations, delete data, or trigger external actions. This is a straightforward Read category operation.
From the tool's definition Tool name and description indicate a query/list operation: 'List MISP organisations'. The verb 'list' and the absence of modification language ('create', 'update', 'delete') confirm this is a retrieval-only action with no side effects.
Attacks that exploit this kind of access
List MISP organisations (local and remote sharing partners). 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_list_organisations: 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_list_organisations 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_list_organisations 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_list_organisations. 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_list_organisations 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 →