AI agents call resolve_get_render_status to retrieve information from Resolve without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves/queries the current status of a render job. It performs no modifications, executes no commands, and has no side effects. It is a straightforward read/get operation.
From the tool's definition Check the status of a specific render job
Attacks that exploit this kind of access
Check the status of a specific render job. It is categorised as a Read tool in the Resolve MCP Server, which means it retrieves data without modifying state.
Register the Resolve MCP server in PolicyLayer and add a rule for resolve_get_render_status: 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.
resolve_get_render_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the resolve_get_render_status 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.
Set action: deny in the PolicyLayer policy for resolve_get_render_status. 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.
resolve_get_render_status 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →