// MCP TOOL REFERENCE

pilot_resume

ServerPilot
CategoryExecute

WHAT PILOT_RESUME ON PILOT DOES

AI agents invoke pilot_resume to trigger actions in Pilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

THE RISK

High Risk

This tool re-engages automated browser control via Playwright, transitioning from manual to automated operation. It triggers the resumption of an automation session that can then perform arbitrary browser actions. While the tool itself doesn't directly execute a specific action, it re-enables automated execution of subsequent browser operations, making Execute the most appropriate category.

From the tool's definition Resume automated control after a pilot_handoff session... return to automated control... A fresh accessibility snapshot of the current page state, ready for continued interaction.

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

HOW TO CONTROL PILOT_RESUME

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_resume:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pilot_resume": {
      "limits": [
        {
          "counter": "pilot_resume_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

pilot_resume stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

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.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More Pilot tools

Destructive pilot_geolocation Set or clear the browser 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

All 61 Pilot tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in Pilot → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-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_resume tool do? +

Resume automated control after a pilot_handoff session. Use when the user has finished manual interaction in the headed browser (e.g., solved a CAPTCHA, completed auth) and wants to return to automated control. Parameters: (none) Returns: A fresh accessibility snapshot of the current page state, ready for continued interaction. Errors: -. It is categorised as a Execute tool in the Pilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pilot_resume? +

Register the Pilot MCP server in PolicyLayer and add a rule for pilot_resume: 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_resume? +

pilot_resume is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pilot_resume? +

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

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

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

pilot_resume

// WHAT PILOT_RESUME ON PILOT DOES

// THE RISK

// HOW TO CONTROL PILOT_RESUME

// EXPLORE