send_location
AI agents use send_location to create or update resources in PyWA MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PyWA MCP Server environment.
This tool sends location data via WhatsApp, which creates a new message artifact with side effects (location is transmitted to a recipient). This is reversible communication (message can be deleted) rather than permanent data destruction. The impact is moderate—an agent could spam locations or send to wrong recipients, but lacks financial consequences or permanent data destruction.
From the tool's definition Tool name 'send_location' combined with server description stating it 'Provides comprehensive WhatsApp Business API functionality with... tools for sending messages, media, interactive buttons/lists, templates, reactions'.
Attacks that exploit this kind of access
send_location. It is categorised as a Write tool in the PyWA MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PyWA MCP Server MCP server in PolicyLayer and add a rule for 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 PyWA MCP Server. Nothing to install.
send_location is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
send_location is provided by the PyWA MCP Server MCP server (jem-hr/pywa-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →