DISCOVERY: attempt to set a clip
AI agents use set_clip_lut to create or update resources in Media-Editor-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Media-Editor-MCP environment.
This tool creates or modifies video clip properties (LUT/color grading) reversibly—a classic Write operation. It is not Destructive (changes are reversible), not Execute (no arbitrary code/shell execution), not Financial, and not a simple Read. While the description is vague ('DISCOVERY: attempt to set'), the name and server context clearly indicate Write.
From the tool's definition Tool name 'set_clip_lut' suggests modifying a clip's look-up table (LUT), a color grading parameter. The description states 'attempt to set a clip,' confirming a modification operation.
Attacks that exploit this kind of access
DISCOVERY: attempt to set a clip. It is categorised as a Write tool in the Media-Editor-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Media-Editor- MCP server in PolicyLayer and add a rule for set_clip_lut: 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 Media-Editor-MCP. Nothing to install.
set_clip_lut 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 set_clip_lut 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 set_clip_lut. 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.
set_clip_lut is provided by the Media-Editor- MCP server (nguyenph88/media-editor-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 →