whatsapp_reject_call · WSAPI WhatsApp MCP Server MCP

WHAT IT DOES

What whatsapp_reject_call does on WSAPI WhatsApp MCP Server

AI agents invoke whatsapp_reject_call to trigger actions in WSAPI WhatsApp MCP Server. 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 IT NEEDS A POLICY

Why whatsapp_reject_call needs a policy

This tool triggers an external operation (rejecting an incoming WhatsApp call) that has real-time side effects on an active session. It is not purely reading data, nor does it delete/overwrite data irreversibly or involve finances. It executes an action against an external service (the WhatsApp session), making Execute the most appropriate category. Misuse could disrupt legitimate communications.

From the tool's definition Reject an incoming call

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

whatsapp_reject_call Rate-limited

whatsapp_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "whatsapp_reject_call": {
      "limits": [
        {
          "counter": "whatsapp_reject_call_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches WSAPI WhatsApp MCP Server, so you can run agents against it safely.

FAQ

Questions about whatsapp_reject_call

What does the whatsapp_reject_call tool do? +

Reject an incoming call. It is categorised as a Execute tool in the WSAPI WhatsApp MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on whatsapp_reject_call? +

Register the WSAPI WhatsApp MCP Server MCP server in PolicyLayer and add a rule for whatsapp_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 WSAPI WhatsApp MCP Server. Nothing to install.

What risk level is whatsapp_reject_call? +

whatsapp_reject_call is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit whatsapp_reject_call? +

Yes. Add a rate_limit block to the whatsapp_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.

How do I block whatsapp_reject_call completely? +

Set action: deny in the PolicyLayer policy for whatsapp_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.

What MCP server provides whatsapp_reject_call? +

whatsapp_reject_call is provided by the WSAPI WhatsApp MCP Server MCP server (wsapi-chat/wsapi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

whatsapp_reject_call is one line of WSAPI WhatsApp MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →