whatsapp_send_location · WSAPI WhatsApp MCP Server MCP

WHAT IT DOES

What whatsapp_send_location does on WSAPI WhatsApp MCP Server

AI agents use whatsapp_send_location to create or update resources in WSAPI WhatsApp MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WSAPI WhatsApp MCP Server environment.

WHY IT NEEDS A POLICY

Why whatsapp_send_location needs a policy

This tool sends a message containing location data to a WhatsApp chat. While the message itself can be deleted, the action creates new data in WhatsApp's system. It is not merely reading data (Read), nor does it execute arbitrary code or shell commands (Execute), delete irreversibly (Destructive), or involve financial transactions (Financial).

From the tool's definition Tool name and description: 'whatsapp_send_location' - 'Send a location message.' This sends/creates data (a message) in WhatsApp, affecting the chat history and recipient experience. The message is reversible (can be deleted by user or recipient).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

whatsapp_send_location Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "whatsapp_send_location": {
      "limits": [
        {
          "counter": "whatsapp_send_location_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_send_location

What does the whatsapp_send_location tool do? +

Send a location message. It is categorised as a Write tool in the WSAPI WhatsApp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on whatsapp_send_location? +

Register the WSAPI WhatsApp MCP Server MCP server in PolicyLayer and add a rule for whatsapp_send_location: 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_send_location? +

whatsapp_send_location is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit whatsapp_send_location? +

Yes. Add a rate_limit block to the whatsapp_send_location 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_send_location completely? +

Set action: deny in the PolicyLayer policy for whatsapp_send_location. 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_send_location? +

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