pinchtab_navigate · Pinchtab MCP: Risk & Policy

WHAT IT DOES

What pinchtab_navigate does on Pinchtab

AI agents invoke pinchtab_navigate to trigger actions in Pinchtab. 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 pinchtab_navigate needs a policy

Navigation is an Execute category action—it causes the browser to fetch and render content from an arbitrary URL, triggering network requests and executing remote code (JavaScript) on that page. The outcome depends entirely on what the attacker provides as the URL argument.

From the tool's definition Tool description states 'Navigate the browser to a URL' with automatic page load handling. This is browser automation that triggers external operations (page navigation and rendering) whose effects depend on the URL argument.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pinchtab_navigate Rate-limited

pinchtab_navigate 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": {
    "pinchtab_navigate": {
      "limits": [
        {
          "counter": "pinchtab_navigate_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 Pinchtab, so you can run agents against it safely.

FAQ

Questions about pinchtab_navigate

What does the pinchtab_navigate tool do? +

Navigate the browser to a URL. Set waitMs to wait for page load and get a snapshot back automatically. It is categorised as a Execute tool in the Pinchtab MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pinchtab_navigate? +

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

What risk level is pinchtab_navigate? +

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

Can I rate-limit pinchtab_navigate? +

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

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

pinchtab_navigate is provided by the Pinchtab MCP server (maderwin/pinchtab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.