send_location_message · Zappaz MCP Server MCP: Risk & Policy

WHAT IT DOES

What send_location_message does on Zappaz MCP Server

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

WHY IT NEEDS A POLICY

Why send_location_message needs a policy

This tool creates and sends a new location message via WhatsApp API, which is a reversible write operation. It modifies state (adds a message to a conversation) but does not delete, execute arbitrary code, or move financial resources.

From the tool's definition Tool name 'send_location_message' and description 'Envia uma mensagem com uma localização por endereço ou coordenadas atraves da Zappaz API' (sends a message with a location by address or coordinates through the Zappaz API) indicates creation of a new…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_location_message Rate-limited

send_location_message 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": {
    "send_location_message": {
      "limits": [
        {
          "counter": "send_location_message_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 Zappaz MCP Server, so you can run agents against it safely.

FAQ

Questions about send_location_message

What does the send_location_message tool do? +

Envia uma mensagem com uma localização por endereço ou coordenadas atraves da Zappaz API. It is categorised as a Write tool in the Zappaz 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 send_location_message? +

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

What risk level is send_location_message? +

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

Can I rate-limit send_location_message? +

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

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

send_location_message is provided by the Zappaz MCP Server MCP server (viiniolliveira/zappaz-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.