reload_tab · Pigeon MCP: Risk & Policy

WHAT IT DOES

What reload_tab does on Pigeon

AI agents invoke reload_tab to trigger actions in Pigeon. 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.

WHY IT NEEDS A POLICY

Why reload_tab needs a policy

Reloading a browser tab triggers an external browser operation with real side effects: it re-executes page scripts, re-fires network requests, and resets page state. This is an action that 'runs' or 'triggers external operations' rather than merely reading data, placing it in the Execute category. Misuse could interrupt active sessions or re-trigger side-effectful page logic.

From the tool's definition Reload a dev tab via the Pigeon extension

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reload_tab Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pigeon, so you can run agents against it safely.

FAQ

Questions about reload_tab

What does the reload_tab tool do? +

Reload a dev tab via the Pigeon extension (active localhost tab by default). It is categorised as a Execute tool in the Pigeon MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reload_tab? +

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

What risk level is reload_tab? +

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

Can I rate-limit reload_tab? +

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

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

reload_tab is provided by the Pigeon MCP server (pepperonas/pigeon). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.