Send media (image, video, document, audio) via WhatsApp.
AI agents use send_media to create or update resources in WhatsApp MCP Stream — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WhatsApp MCP Stream environment.
This tool creates and sends new messages with media attachments to WhatsApp contacts or groups. While reversible in principle (messages can be deleted), the primary action is writing/creating new data (outbound messages) with moderate blast radius: an agent could spam contacts, send malicious files, or impersonate the user to damage relationships or reputation.
From the tool's definition Tool name 'send_media' and description 'Send media (image, video, document, audio) via WhatsApp' indicate creation and transmission of outbound messages through a messaging platform.
Attacks that exploit this kind of access
Send media (image, video, document, audio) via WhatsApp. It is categorised as a Write tool in the WhatsApp MCP Stream MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WhatsApp MCP Stream MCP server in PolicyLayer and add a rule for send_media: 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 WhatsApp MCP Stream. Nothing to install.
send_media 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_media 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_media. 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_media is provided by the WhatsApp MCP Stream MCP server (loglux/whatsapp-mcp-stream). 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 →