resolve_stop_render · Resolve MCP: Risk & Policy

WHAT IT DOES

What resolve_stop_render does on Resolve

AI agents invoke resolve_stop_render to trigger actions in Resolve. 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 resolve_stop_render needs a policy

Stopping a render is an operational action that terminates an active process. It is not purely destructive (no data is deleted), but it executes a control action that affects an ongoing external operation. The blast radius is medium: stopping a render wastes compute time and may leave partial output files, but is generally recoverable by restarting the render.

From the tool's definition 'Stop the current render in progress' — this interrupts an ongoing render operation, which is an external process execution side effect.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_stop_render Rate-limited

resolve_stop_render 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": {
    "resolve_stop_render": {
      "limits": [
        {
          "counter": "resolve_stop_render_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 Resolve, so you can run agents against it safely.

FAQ

Questions about resolve_stop_render

What does the resolve_stop_render tool do? +

Stop the current render in progress. It is categorised as a Execute tool in the Resolve MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on resolve_stop_render? +

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

What risk level is resolve_stop_render? +

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

Can I rate-limit resolve_stop_render? +

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

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

resolve_stop_render is provided by the Resolve MCP server (jenkinsm13/resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.