Set the audio of a video clip.
AI agents use set_audio to create or update resources in vidMagik-mcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your vidMagik-mcp environment.
This tool modifies video clips by setting their audio track, which is a write operation. While video/audio files themselves remain on disk, the clip object's state is changed. The operation is reversible (audio can be replaced with different audio or removed), so it does not qualify as Destructive.
From the tool's definition The tool name 'set_audio' and description 'Set the audio of a video clip' indicate the tool modifies video clip metadata/content by attaching or replacing audio. This is a modification operation that creates or changes data in a reversible manner.
Attacks that exploit this kind of access
Set the audio of a video clip. It is categorised as a Write tool in the vidMagik-mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the vidMagik- MCP server in PolicyLayer and add a rule for set_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 vidMagik-mcp. Nothing to install.
set_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 set_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 set_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.
set_audio is provided by the vidMagik- MCP server (vizionik25/vidmagik-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 →