resume_run · MEMGRAPH- MCP: Risk & Policy

WHAT IT DOES

What resume_run does on MEMGRAPH-MCP

AI agents invoke resume_run to trigger actions in MEMGRAPH-MCP. 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 resume_run needs a policy

Resuming an orchestrator run re-initiates active execution of a multi-agent workflow (coding, review, repair, CI, approval). This triggers external operations across agents whose effects depend on the run's state and arguments. It spans Execute territory at minimum, with potentially broad blast radius if agents perform writes, deploys, or CI operations as part of the run.

From the tool's definition 'Resume an orchestrator run until completion, pause, or failure' — triggers execution of an orchestrator workflow with potentially broad side effects

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resume_run Rate-limited

resume_run 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": {
    "resume_run": {
      "limits": [
        {
          "counter": "resume_run_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 MEMGRAPH-MCP, so you can run agents against it safely.

FAQ

Questions about resume_run

What does the resume_run tool do? +

Resume an orchestrator run until completion, pause, or failure. It is categorised as a Execute tool in the MEMGRAPH-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on resume_run? +

Register the MEMGRAPH- MCP server in PolicyLayer and add a rule for resume_run: 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 MEMGRAPH-MCP. Nothing to install.

What risk level is resume_run? +

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

Can I rate-limit resume_run? +

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

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

resume_run is provided by the MEMGRAPH- MCP server (mikeb317/memgraph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.