AI agents invoke send_whatsapp to trigger actions in Mcp Afip. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Sending a WhatsApp message is an external operation that dispatches a message to a recipient. This is not merely writing data in a system — it triggers an outbound communication action via an external platform. An AI agent misusing this could send unsolicited or malicious messages to contacts at scale, making it high severity.
From the tool's definition 'Send a WhatsApp message' — triggers an external messaging operation with real-world side effects
Documented attack patterns abuse exactly the kind of access send_whatsapp gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Afip, and nothing reaches the server without passing your rules. This is the rule we recommend for send_whatsapp:
{
"version": "1",
"default": "deny",
"tools": {
"send_whatsapp": {
"limits": [
{
"counter": "send_whatsapp_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} send_whatsapp stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Send a WhatsApp message. It is categorised as a Execute tool in the Mcp Afip MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for send_whatsapp: 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 Mcp Afip. Nothing to install.
send_whatsapp is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_whatsapp 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_whatsapp. 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_whatsapp is provided by the Mcp Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Afip, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Afip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.