send_template
AI agents use send_template 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.
This tool sends templated messages via WhatsApp, which creates/modifies communication data. It is Write rather than Execute because it appears to execute a pre-defined template rather than arbitrary code. Severity is high because an AI agent could mass-send unsolicited messages to many recipients, causing reputational harm, violating WhatsApp terms of service, or triggering spam complaints.
From the tool's definition Tool name 'send_template' combined with server context describing 'sending messages' and 'templates' through WhatsApp Business API. Sibling tools include send_audio, send_image, send_document, send_contact, send_location—all clearly write/send operations.
Attacks that exploit this kind of access
send_template. 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_template: 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_template 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_template 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_template. 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_template 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 →