resolve_start_render · Resolve MCP: Risk & Policy

WHAT IT DOES

What resolve_start_render does on Resolve

AI agents invoke resolve_start_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_start_render needs a policy

Rendering is an external operation that runs processing jobs, consuming CPU/GPU resources and writing output files. It is not merely writing data reversibly; it triggers a potentially long-running compute process. Misuse could queue and execute unintended renders, wasting resources or overwriting output files.

From the tool's definition 'Start rendering queued jobs' — triggers an external rendering operation that consumes system resources and produces output files

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_start_render Rate-limited

resolve_start_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_start_render": {
      "limits": [
        {
          "counter": "resolve_start_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_start_render

What does the resolve_start_render tool do? +

Start rendering queued jobs. 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_start_render? +

Register the Resolve MCP server in PolicyLayer and add a rule for resolve_start_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_start_render? +

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

Can I rate-limit resolve_start_render? +

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

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

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