撤销应用运行时权限，如 android.permission.CAMERA
AI agents call revoke_permission to permanently remove resources in Android ADB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call revoke_permission doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Android ADB MCP Server is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
撤销应用运行时权限，如 android.permission.CAMERA. It is categorised as a Destructive tool in the Android ADB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Android ADB MCP Server MCP server in PolicyLayer and add a rule for revoke_permission: 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.
revoke_permission is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the revoke_permission 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 revoke_permission. 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.
revoke_permission 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.