misp_publish_event · Misp MCP: Risk & Policy

WHAT IT DOES

What misp_publish_event does on Misp

AI agents invoke misp_publish_event to trigger actions in Misp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why misp_publish_event needs a policy

Publishing a MISP event triggers external notifications and alerts to sharing partners — this is an external operation with broad reach. It is not merely writing data internally; it actively propagates intelligence to third parties, making it an Execute-level action.

From the tool's definition Publish a MISP event, triggering alerts and notifications to sharing partners. State-changing: requires confirm:true

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

misp_publish_event Rate-limited

misp_publish_event stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "misp_publish_event": {
      "limits": [
        {
          "counter": "misp_publish_event_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Misp, so you can run agents against it safely.

FAQ

Questions about misp_publish_event

What does the misp_publish_event tool do? +

Publish a MISP event, triggering alerts and notifications to sharing partners. State-changing: requires confirm:true (or MISP_ALLOW_DESTRUCTIVE=true). It is categorised as a Execute tool in the Misp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on misp_publish_event? +

Register the Misp MCP server in PolicyLayer and add a rule for misp_publish_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.

What risk level is misp_publish_event? +

misp_publish_event is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit misp_publish_event? +

Yes. Add a rate_limit block to the misp_publish_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.

How do I block misp_publish_event completely? +

Set action: deny in the PolicyLayer policy for misp_publish_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.

What MCP server provides misp_publish_event? +

misp_publish_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.