start_change_resolution
AI agents invoke start_change_resolution 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 process video files. While video conversion itself is reversible (Write-like), the tool initiates external processes whose side effects are determined by user-supplied arguments. An AI agent could misuse this to process arbitrary files, consume computational resources, or convert videos in unintended ways.
From the tool's definition Tool name 'start_change_resolution' and sibling tools like 'start_audio_extraction', 'start_trim', 'start_change_format' indicate this initiates FFmpeg operations.
Attacks that exploit this kind of access
start_change_resolution. 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_resolution: 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_resolution 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_resolution 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_resolution. 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_resolution 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 →