AI agents invoke add_text_overlay to trigger actions in Video & Audio Editing MCP Server. 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.
Based on the server context and sibling tools (add_image_overlay, add_subtitles, etc.), this tool likely runs FFmpeg commands to render text onto video frames, constituting an Execute action. The empty description lowers confidence. Severity is medium as it modifies media files but is generally reversible.
From the tool's definition Tool name 'add_text_overlay' on a server that 'enables AI assistants to perform professional-grade operations including format conversion, trimming, overlays, transitions, and advanced audio processing' via FFmpeg. The description is empty.
Documented attack patterns abuse exactly the kind of access add_text_overlay gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Video & Audio Editing MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_text_overlay:
{
"version": "1",
"default": "deny",
"tools": {
"add_text_overlay": {
"limits": [
{
"counter": "add_text_overlay_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}add_text_overlay stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
add_text_overlay. It is categorised as a Execute tool in the Video & Audio Editing MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Video & Audio Editing MCP Server MCP server in PolicyLayer and add a rule for add_text_overlay: 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 Video & Audio Editing MCP Server. Nothing to install.
add_text_overlay 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 add_text_overlay 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_text_overlay. 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_text_overlay is provided by the Video & Audio Editing MCP Server MCP server (misbahsy/video-audio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Video & Audio Editing MCP 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.
27 Video & Audio Editing MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.