AI agents use misp_attach_galaxy_cluster to create or update resources in Misp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Misp environment.
The tool adds metadata (galaxy cluster associations like MITRE ATT&CK techniques or threat actors) to existing MISP objects. This is a write operation: it creates new associations and modifies the state of events/attributes. It is reversible (clusters can be detached), distinguishing it from Destructive. It does not execute code, move money, or permanently delete data.
From the tool's definition Attach a galaxy cluster...to an event or attribute—this modifies event or attribute metadata by adding a relationship/association, which is a reversible write operation.
Attacks that exploit this kind of access
Attach a galaxy cluster (MITRE ATT&CK technique, threat actor, etc.) to an event or attribute. It is categorised as a Write tool in the Misp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Misp MCP server in PolicyLayer and add a rule for misp_attach_galaxy_cluster: 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_attach_galaxy_cluster is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the misp_attach_galaxy_cluster 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_attach_galaxy_cluster. 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_attach_galaxy_cluster 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 →