retry_process · Morpheus MCP Server MCP: Risk & Policy

WHAT IT DOES

What retry_process does on Morpheus MCP Server

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

Retrying a failed process re-executes an operation, which constitutes triggering an external operation. The blast radius is medium since it re-runs something that already failed, potentially causing duplicate actions or unintended side effects depending on the process type, but it does not inherently delete data or move money.

From the tool's definition 'Retry a failed process' — triggers re-execution of a previously failed process/workflow

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

retry_process Rate-limited

retry_process 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": {
    "retry_process": {
      "limits": [
        {
          "counter": "retry_process_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 Morpheus MCP Server, so you can run agents against it safely.

FAQ

Questions about retry_process

What does the retry_process tool do? +

Retry a failed process. It is categorised as a Execute tool in the Morpheus MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on retry_process? +

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

What risk level is retry_process? +

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

Can I rate-limit retry_process? +

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

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

retry_process is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.