pinchtab_wait · Pinchtab MCP: Risk & Policy

WHAT IT DOES

What pinchtab_wait does on Pinchtab

AI agents invoke pinchtab_wait 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_wait needs a policy

This tool executes a time-blocking operation rather than merely reading or writing data. However, severity is low because the blast radius of misusing a delay is minimal—the worst outcome is wasted time or disrupted automation flow. It does not modify data, delete anything, move money, or execute arbitrary code.

From the tool's definition Tool performs a time-delay operation that blocks execution for a specified duration. While semantically a 'wait' function, it is an executable action that affects program flow and timing behavior.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pinchtab_wait Rate-limited

pinchtab_wait 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_wait": {
      "limits": [
        {
          "counter": "pinchtab_wait_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_wait

What does the pinchtab_wait tool do? +

Wait for a specified number of seconds. Useful after navigation or dynamic content loading. 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_wait? +

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

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

Can I rate-limit pinchtab_wait? +

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

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

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