Send a message using a template
AI agents use send_template to create or update resources in Evolution API WhatsApp MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Evolution API WhatsApp MCP Server environment.
This tool creates and modifies communication state by sending WhatsApp messages, which is fundamentally a write operation. It is not destructive (messages can be recalled/deleted), not financial (no money moves), and not execute (no arbitrary code/command execution, though it does trigger external messaging).
From the tool's definition Tool name 'send_template' and description 'Send a message using a template' indicates the tool creates and transmits messages through WhatsApp Business.
Attacks that exploit this kind of access
Send a message using a template. It is categorised as a Write tool in the Evolution API WhatsApp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Evolution API WhatsApp 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 Evolution API WhatsApp 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 Evolution API WhatsApp MCP Server MCP server (luiso2/mcp-evolution-api). 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 →