High Risk →

pilot_forward

Navigate forward to the next page in browser history. Use when the user wants to go forward after using pilot_back. Parameters: (none) Returns: The URL of the page after navigating forward. Errors: -

How to control pilot_forward ↓

AI agents invoke pilot_forward 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.

High Risk

This tool triggers a browser navigation action (moving forward in history), which is an external operation that changes the browser's state. It doesn't merely read data but actively controls the browser, making it an Execute category.

From the tool's definition Navigate forward to the next page in browser history

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "pilot_forward": {
      "limits": [
        {
          "counter": "pilot_forward_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Pilot — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the pilot_forward tool do? +

Navigate forward to the next page in browser history. Use when the user wants to go forward after using pilot_back. Parameters: (none) Returns: The URL of the page after navigating forward. 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_forward? +

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

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

Can I rate-limit pilot_forward? +

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

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

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

Free to start. No card required.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.