AI agents use resolve_clear_clip_mark_in_out 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 clip properties by clearing mark in/out points, which are editable metadata attributes of a media pool clip. This is reversible—mark points can be re-added or reset. The operation affects only the clip's internal editing metadata, not the underlying media file or project structure. This qualifies as Write (creates or modifies data reversibly) rather than Read, Execute, or Destructive.
From the tool's definition Tool name 'resolve_clear_clip_mark_in_out' and description 'Clear mark in/out points on a media pool clip' indicate modification of clip metadata (mark in/out points).
Attacks that exploit this kind of access
Clear mark in/out points on a media pool clip. 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_clear_clip_mark_in_out: 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_clear_clip_mark_in_out 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_clear_clip_mark_in_out 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_clear_clip_mark_in_out. 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_clear_clip_mark_in_out 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 →