misp_cache_feed · Misp MCP: Risk & Policy

WHAT IT DOES

What misp_cache_feed does on Misp

AI agents invoke misp_cache_feed 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_cache_feed needs a policy

This tool fetches remote feed data and writes it to local storage (caching), which is a side-effecting operation that modifies local state. It is not purely a read (it persists data locally), not a write to MISP event data, and not destructive or financial. 'Execute' best captures the triggered external operation of fetching and caching data locally.

From the tool's definition Cache feed data locally for correlation without creating events

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

misp_cache_feed Rate-limited

misp_cache_feed 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_cache_feed": {
      "limits": [
        {
          "counter": "misp_cache_feed_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_cache_feed

What does the misp_cache_feed tool do? +

Cache feed data locally for correlation without creating events. 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_cache_feed? +

Register the Misp MCP server in PolicyLayer and add a rule for misp_cache_feed: 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_cache_feed? +

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

Can I rate-limit misp_cache_feed? +

Yes. Add a rate_limit block to the misp_cache_feed 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_cache_feed completely? +

Set action: deny in the PolicyLayer policy for misp_cache_feed. 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_cache_feed? +

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

// THE FULL RECORD

misp_cache_feed is one line of Misp's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →