pilot_geolocation

THE RISK

Critical Risk

An AI agent that decides to call pilot_geolocation doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Pilot is gone — there is no undo for destructive operations.

Documented attack patterns abuse exactly the kind of access pilot_geolocation gives an agent:

HOW TO CONTROL PILOT_GEOLOCATION

PolicyLayer is an MCP gateway — it sits between your AI agents and Pilot, and nothing reaches the server without passing your rules. This is the rule we recommend for pilot_geolocation:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "pilot_geolocation"
  ]
}

pilot_geolocation disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Pilot — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More Pilot tools

Execute pilot_frame_reset Switch the browser context back to the main page frame after working inside an iframe. Use Execute pilot_reload Reload the current page, waiting for DOM content to load. Use when the user wants to refre Execute pilot_evaluate Execute a JavaScript expression or function in the browser page context and return the res Execute pilot_hover Hover the mouse over an element, triggering hover states, tooltips, and dropdown menus. Us Execute pilot_intercept Intercept network requests matching a URL pattern and respond with custom status, headers, Execute pilot_navigate Navigate the browser to a URL and wait for DOM content to load. Use when the user wants to Execute pilot_tab_new Open a new browser tab, optionally navigating to a URL. Use when the user wants to open a Execute pilot_wait Wait for a specific condition before proceeding — an element to appear, the network to bec

All 61 Pilot tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in Pilot → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the pilot_geolocation tool do? +

Set or clear the browser. It is categorised as a Destructive tool in the Pilot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on pilot_geolocation? +

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

What risk level is pilot_geolocation? +

pilot_geolocation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit pilot_geolocation? +

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

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

pilot_geolocation is provided by the Pilot MCP server (tacosyhorchata/pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pilot tool call.

Deterministic rules across all 61 Pilot tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN PILOT →

Free to start. No card required.

61 Pilot tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT PILOT_GEOLOCATION ON PILOT DOES

// THE RISK

// HOW TO CONTROL PILOT_GEOLOCATION

// EXPLORE