adb_input_pinch
Perform a multi-touch pinch (zoom out) or spread (zoom in) gesture. Two fingers move symmetrically toward or away from a center point. Uses parallel swipe injection by default (universal, no root); when root is available, can use raw sendevent for true multi-touch MT protocol injection. The
This record as markdown: /tools/io-github-fullread-deepadb/adb-input-pinch.md
What adb_input_pinch does on Deepadb
AI agents invoke adb_input_pinch to trigger actions in Deepadb. 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 adb_input_pinch is rated High
This tool executes touch/gesture input commands on an Android device via ADB, triggering external UI interactions. It injects input events into the device's input system, which constitutes executing an operation with real effects on the device state. While not destructive on its own, misuse could trigger unintended UI actions (e.g., zooming into sensitive content, triggering UI elements).
From the tool's definition Perform a multi-touch pinch (zoom out) or spread (zoom in) gesture... Uses parallel swipe injection... can use raw sendevent for true multi-touch MT protocol injection
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs adb_input_pinch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_input_pinch, this is the rule to start with:
adb_input_pinch 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_input_pinch call is checked against it from then on.
Questions about adb_input_pinch
Perform a multi-touch pinch (zoom out) or spread (zoom in) gesture. Two fingers move symmetrically toward or away from a center point. Uses parallel swipe injection by default (universal, no root); when root is available, can use raw sendevent for true multi-touch MT protocol injection. The. It is categorised as a Execute tool in the Deepadb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_input_pinch: 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 Deepadb. Nothing to install.
adb_input_pinch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the adb_input_pinch 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.
Set action: deny in the PolicyLayer policy for adb_input_pinch. 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.
adb_input_pinch is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
Across the catalogue