add_audio
AI agents use add_audio 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 'add_' prefix and media-editing context strongly suggest this tool creates or modifies audio tracks within CapCut or Premiere Pro projects, a reversible Write operation. Severity is medium because audio insertion could alter project timing/sync unexpectedly if misused by an agent, but changes are undoable.
From the tool's definition Tool name 'add_audio' with prefix 'add_' indicates creation/insertion of audio content into media projects. Context: sibling tools like 'add_animation', 'add_captions', 'add_clip_effect', 'add_text' are all Write operations.
Attacks that exploit this kind of access
add_audio. 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_audio: 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_audio 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_audio 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_audio. 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_audio 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 →