Add one or more contacts to the WhatsApp address book. Accepts an array of contacts.
AI agents use add_contacts to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.
This tool creates new contact records in WhatsApp's address book. While reversible (contacts can be deleted), it modifies user data and could be misused to spam or manipulate communications by injecting contacts without authorization.
From the tool's definition The tool description states it will 'Add one or more contacts to the WhatsApp address book,' which is a create/modify operation that adds data to a contact list.
Documented attack patterns abuse exactly the kind of access add_contacts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for add_contacts:
{
"version": "1",
"default": "deny",
"tools": {
"add_contacts": {
"limits": [
{
"counter": "add_contacts_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_contacts stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add one or more contacts to the WhatsApp address book. Accepts an array of contacts. It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for add_contacts: 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 Ap2. Nothing to install.
add_contacts 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 add_contacts 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 add_contacts. 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.
add_contacts is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, 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 Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.