wa_reject_call
Reject an incoming voice or video call. The call ID is received via the whatsapp/call.received notification.
This record as markdown: /tools/delltrak-wamcp/wa-reject-call.md
What wa_reject_call does on WA MCP
AI agents invoke wa_reject_call to trigger actions in WA MCP. 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.
Why wa_reject_call is rated High
Rejecting a call is an external operation that triggers a real-time response to an incoming call event on WhatsApp. It is not a simple data read or write, but an action that affects an active communication session. It does not destroy data or move money, making Execute the most appropriate category. Misuse could disrupt legitimate calls or be used to systematically reject calls without user awareness.
From the tool's definition Reject an incoming voice or video call
Attacks that exploit this kind of access
The rule that runs wa_reject_call safely
PolicyLayer is an MCP gateway: it sits between your AI agents and WA MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wa_reject_call, this is the rule to start with:
wa_reject_call 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.
The button opens the PolicyLayer dashboard: create your workspace, connect WA MCP, apply this rule, and every wa_reject_call call is checked against it from then on.
Questions about wa_reject_call
Reject an incoming voice or video call. The call ID is received via the whatsapp/call.received notification. It is categorised as a Execute tool in the WA MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the WA MCP server in PolicyLayer and add a rule for wa_reject_call: 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 WA MCP. Nothing to install.
wa_reject_call 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 wa_reject_call 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 wa_reject_call. 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.
wa_reject_call is provided by the WA MCP server (delltrak/wamcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on WA, and thousands of servers like it.
This server
Across the catalogue