pinchtab_scroll · Pinchtab MCP: Risk & Policy

WHAT IT DOES

What pinchtab_scroll does on Pinchtab

AI agents invoke pinchtab_scroll 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_scroll needs a policy

Scrolling is a browser UI action that causes external side effects (changing the visible viewport or element scroll position in Chrome). It doesn't read, write, or delete data, but it executes an operation in the browser. Misuse potential is low since scrolling itself causes no data loss or financial impact, but it is an active browser automation action rather than a passive read.

From the tool's definition 'Scroll the page or a specific element. Supports all four directions.' — triggers a browser interaction/action

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pinchtab_scroll Rate-limited

pinchtab_scroll 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_scroll": {
      "limits": [
        {
          "counter": "pinchtab_scroll_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_scroll

What does the pinchtab_scroll tool do? +

Scroll the page or a specific element. Supports all four directions. 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_scroll? +

Register the Pinchtab MCP server in PolicyLayer and add a rule for pinchtab_scroll: 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_scroll? +

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

Can I rate-limit pinchtab_scroll? +

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

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

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