add_captions
AI agents use add_captions 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 captions in a video project, which is a reversible write operation. The description is empty, reducing confidence slightly. Severity is medium because caption changes could alter project output significantly, but are easily undone and carry no financial or destructive impact. The tool operates within an editing context where modifications are expected and reversible.
From the tool's definition Tool named 'add_captions' on a media editing server (CapCut/Adobe Premiere Pro control). The 'add_' prefix and context of sibling tools (add_animation, add_audio, add_text, add_filter, etc.) indicate creation/modification of media elements.
Attacks that exploit this kind of access
add_captions. 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 add_captions: 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.
add_captions 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 add_captions 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 add_captions. 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.
add_captions 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 →