place_clip
AI agents use place_clip 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.
The tool appears to insert or reposition media elements within a video project, which is a reversible modification operation (Write category). Severity is medium because misuse could corrupt a video project or waste processing resources, but changes are typically undoable in video editing software. Confidence is 0.7 due to absent description and reliance on contextual inference from sibling tools and name alone.
From the tool's definition Tool name 'place_clip' suggests creating or modifying video composition by positioning clips; sibling tools like 'add_animation', 'add_audio', 'add_captions', 'add_filter' all modify video content. No description provided, limiting specificity.
Attacks that exploit this kind of access
place_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 place_clip: 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.
place_clip 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 place_clip 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 place_clip. 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.
place_clip 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 →