AI agents use send_contact_message to create or update resources in Whatsapp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Whatsapp environment.
This tool creates outbound communication artifacts (contact card messages) via WhatsApp's API. It is a Write operation because it creates new data (messages) with side effects (delivery to recipients), but it is not Destructive (not deletion/overwrite), not Execute (no arbitrary code execution), and not Financial (no money movement).
From the tool's definition Tool name is 'send_contact_message' and description states 'Send one or more contact cards.' This performs a sending action that creates/modifies state in WhatsApp (outbound messages are recorded, conversations are updated).
Attacks that exploit this kind of access
Send one or more contact cards. It is categorised as a Write tool in the Whatsapp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Whatsapp MCP server in PolicyLayer and add a rule for send_contact_message: 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. Nothing to install.
send_contact_message 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_contact_message 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_contact_message. 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_contact_message is provided by the Whatsapp MCP server (spirit122/whatsapp-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 →