在指定中心点执行缩放手势，scale>1 放大，scale<1 缩小
AI agents invoke pinch_zoom to trigger actions in Android ADB MCP Server. 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.
pinch_zoom triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
在指定中心点执行缩放手势，scale>1 放大，scale<1 缩小. It is categorised as a Execute tool in the Android ADB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Android ADB MCP Server MCP server in PolicyLayer and add a rule for pinch_zoom: 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 Android ADB MCP Server. Nothing to install.
pinch_zoom 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 pinch_zoom 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 pinch_zoom. 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.
pinch_zoom is provided by the Android ADB MCP Server MCP server (xuegao-tzx/android-adb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.