start_change_format
AI agents invoke start_change_format to trigger actions in Mcp Ffmpeg. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes FFmpeg commands to convert video/audio formats, which are irreversible transformations of media files. Format conversion is a compute operation whose output depends on the input file and format arguments provided. While not immediately destructive (the original file typically remains), execution of media processing commands with arbitrary parameters qualifies as Execute rather than Write.
From the tool's definition Tool name 'start_change_format' paired with server context describing 'FFmpeg wrapper enabling AI assistants to perform video processing tasks such as trimming, format conversion, resolution change, and subtitle conversion' indicates this tool triggers…
Attacks that exploit this kind of access
start_change_format. It is categorised as a Execute tool in the Mcp Ffmpeg MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Ffmpeg MCP server in PolicyLayer and add a rule for start_change_format: 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 Mcp Ffmpeg. Nothing to install.
start_change_format is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_change_format 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 start_change_format. 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.
start_change_format is provided by the Mcp Ffmpeg MCP server (priyanshum143/mcp-ffmpeg). 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 →