idb_tap · Xclaude Plugin MCP: Risk & Policy

WHAT IT DOES

What idb_tap does on Xclaude Plugin

AI agents invoke idb_tap to trigger actions in Xclaude Plugin. 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 idb_tap needs a policy

Tapping at UI coordinates drives simulator UI interactions (button presses, navigation, form submissions, etc.). The effect depends entirely on what is at those coordinates, making this an Execute-class action. Misuse could trigger unintended app actions, but is limited to the simulator context, hence medium severity.

From the tool's definition 'Tap at UI coordinates' — triggers a UI interaction/gesture on a simulator, which is an external operation whose effects depend on the coordinates provided

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

idb_tap Rate-limited

idb_tap 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": {
    "idb_tap": {
      "limits": [
        {
          "counter": "idb_tap_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 Xclaude Plugin, so you can run agents against it safely.

FAQ

Questions about idb_tap

What does the idb_tap tool do? +

Tap at UI coordinates. It is categorised as a Execute tool in the Xclaude Plugin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on idb_tap? +

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

What risk level is idb_tap? +

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

Can I rate-limit idb_tap? +

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

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

idb_tap is provided by the Xclaude Plugin MCP server (conorluddy/xclaude-plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

idb_tap is one line of Xclaude Plugin's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →