stop_location_share · WhatsApp MCP Automation MCP

WHAT IT DOES

What stop_location_share does on WhatsApp MCP Automation

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

WHY IT NEEDS A POLICY

Why stop_location_share needs a policy

This tool terminates an active live location sharing session. It modifies state (ends a broadcast) but is not truly irreversible in the destructive sense — location sharing can be restarted. It's a Write/state-change action. Misuse could expose or conceal a user's location status, hence medium severity.

From the tool's definition Stop sharing live location

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_location_share Rate-limited

stop_location_share 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": {
    "stop_location_share": {
      "limits": [
        {
          "counter": "stop_location_share_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 WhatsApp MCP Automation, so you can run agents against it safely.

FAQ

Questions about stop_location_share

What does the stop_location_share tool do? +

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

How do I enforce a policy on stop_location_share? +

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

What risk level is stop_location_share? +

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

Can I rate-limit stop_location_share? +

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

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

stop_location_share is provided by the WhatsApp MCP Automation MCP server (priyasogani8-star/whatsapp-mcp-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.