Send an audio message.
AI agents use send_audio to create or update resources in PyWA MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PyWA MCP Server environment.
Sending audio messages is a Write operation: it creates and transmits data (audio content) to WhatsApp users, causing state changes in the messaging system. It is reversible (messages can be deleted) and has no permanent data destruction. Severity is medium because misuse could spam users or send unwanted audio content, but lacks the financial impact of payment tools or the irreversible nature of data deletion.
From the tool's definition Tool name 'send_audio' combined with server description stating it 'provides...functionality with...tools for sending messages, media' indicates the tool creates and transmits audio content through WhatsApp Business API.
Attacks that exploit this kind of access
Send an audio message. It is categorised as a Write tool in the PyWA MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PyWA MCP Server MCP server in PolicyLayer and add a rule for send_audio: 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 PyWA MCP Server. Nothing to install.
send_audio 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_audio 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_audio. 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_audio is provided by the PyWA MCP Server MCP server (jem-hr/pywa-mcp-server). 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 →