AI agents use compress-video to create or update resources in MCP Media Processing Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Media Processing Server environment.
Compressing a video creates or overwrites a modified version of the file. This is a reversible write operation (the original may or may not be preserved depending on implementation), but it modifies data rather than executing arbitrary code or deleting irreversibly. Severity is medium because misuse could overwrite or degrade video files at scale.
From the tool's definition 'Compress video file' — modifies a video file by reducing its size/quality
Documented attack patterns abuse exactly the kind of access compress-video gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Media Processing Server, and nothing reaches the server without passing your rules. This is the rule we recommend for compress-video:
{
"version": "1",
"default": "deny",
"tools": {
"compress-video": {
"limits": [
{
"counter": "compress-video_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}compress-video stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Compress video file. It is categorised as a Write tool in the MCP Media Processing Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Media Processing Server MCP server in PolicyLayer and add a rule for compress-video: 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 Media Processing Server. Nothing to install.
compress-video 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 compress-video 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 compress-video. 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.
compress-video is provided by the MCP Media Processing Server MCP server (maoxiaoke/mcp-media-processor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Media Processing Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 MCP Media Processing Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.