AI agents call revoke-permission to permanently remove resources in ADB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Revoking a permission modifies the app's access rights in a way that can break app functionality. While technically 'grant-permission' exists as a sibling tool (implying reversibility), permission revocation is a privileged system operation that can disrupt running apps, cause data loss if the app loses storage/location/camera access mid-use, and may have security implications.
From the tool's definition 'Revoke a specific permission from an app' — removing a permission is an irreversible system-level change that cannot be easily undone without re-granting
Documented attack patterns abuse exactly the kind of access revoke-permission gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ADB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for revoke-permission:
{
"version": "1",
"default": "deny",
"hide": [
"revoke-permission"
]
}revoke-permission disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Revoke a specific permission from an app. It is categorised as a Destructive tool in the ADB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 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 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 ADB MCP Server MCP server (jiantao88/android-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ADB MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
30 ADB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.