AI agents use resolve_update_layout_preset 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.
This tool modifies layout preset settings without deleting them irreversibly. A user can undo the change by re-saving a different layout configuration. While layout changes could affect a user's workflow if misapplied by an agent, the impact is limited to UI/workspace configuration (not financial, not destructive, not executing arbitrary code).
From the tool's definition Tool name contains 'update' and description states 'Overwrite an existing layout preset' — both indicate modification of existing data. The verb 'overwrite' confirms reversible changes to stored layout configuration.
Attacks that exploit this kind of access
Overwrite an existing layout preset with the current layout. 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_update_layout_preset: 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_update_layout_preset 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_update_layout_preset 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_update_layout_preset. 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_update_layout_preset 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 →