send_video
AI agents use send_video to create or update resources in Evolution API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Evolution API MCP Server environment.
Send operations that transmit messages or media are Write-category actions—they create and deliver data with reversible side effects (messages can be deleted). Not Execute because there is no code execution or arbitrary external operation triggering. Not Destructive because sending a video does not erase data.
From the tool's definition Tool name 'send_video' in a WhatsApp messaging context; sibling tools include 'send_image', 'send_audio', 'send_document', and 'send_message' variants. The Evolution API MCP Server description states it enables 'send messages' and 'manage media'.
Attacks that exploit this kind of access
send_video. It is categorised as a Write tool in the Evolution API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Evolution API MCP Server MCP server in PolicyLayer and add a rule for send_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 Evolution API MCP Server. Nothing to install.
send_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 send_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 send_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.
send_video is provided by the Evolution API MCP Server MCP server (pablobispo/evoapi-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 →