AI agents use resolve_set_render_format_and_codec to create or update resources in Resolve — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Resolve environment.
The tool modifies render settings (format and codec), which is reversible configuration change—a Write operation. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or trigger external side effects beyond Resolve's render pipeline.
From the tool's definition Tool name 'resolve_set_render_format_and_codec' and description 'Set the render format and codec' indicate modification of render settings. This changes configuration state in the Resolve project.
Attacks that exploit this kind of access
Set the render format and codec. It is categorised as a Write tool in the Resolve MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Resolve MCP server in PolicyLayer and add a rule for resolve_set_render_format_and_codec: 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_set_render_format_and_codec is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the resolve_set_render_format_and_codec 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_set_render_format_and_codec. 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_set_render_format_and_codec 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 →