Send message with buttons
AI agents use send_buttons 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 sends a WhatsApp message (creates outbound communication), which is a reversible write operation. It does not delete data or execute arbitrary code. Severity is medium because it enables mass messaging or spam if misused, but has limited blast radius compared to destructive or financial actions.
From the tool's definition 'Send message with buttons' — creates and sends a new WhatsApp message with interactive button components to a recipient
Attacks that exploit this kind of access
Send message with buttons. 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_buttons: 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_buttons 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_buttons 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_buttons. 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_buttons 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 →