AI agents call waha_get_contact to retrieve information from WAHA MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves contact information without modifying, deleting, or executing any operations. It is a straightforward query operation that returns data, fitting the Read category.
From the tool's definition Tool name 'waha_get_contact' and description 'Get contact information by ID' indicate data retrieval with no modification, deletion, or side effects.
Documented attack patterns abuse exactly the kind of access waha_get_contact gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WAHA MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for waha_get_contact:
{
"version": "1",
"default": "deny",
"tools": {
"waha_get_contact": {}
}
} waha_get_contact is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get contact information by ID. It is categorised as a Read tool in the WAHA MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WAHA MCP Server MCP server in PolicyLayer and add a rule for waha_get_contact: 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 WAHA MCP Server. Nothing to install.
waha_get_contact is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the waha_get_contact 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 waha_get_contact. 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.
waha_get_contact is provided by the WAHA MCP Server MCP server (seejux/waha-whatsapp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WAHA MCP Server, 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.
52 WAHA MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.