Critical Risk →

reset-permissions

Reset all permissions for a specific package

How to control reset-permissions ↓

What reset-permissions does on ADB MCP Server

AI agents call reset-permissions 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.

Critical Risk

Why reset-permissions needs a policy

Resetting all permissions for a package is an irreversible bulk operation that removes all granted permissions at once. Unlike granting or revoking a single permission, a full reset cannot be easily undone without knowing the prior permission state, potentially breaking app functionality. This is more severe than a simple Write because the action cannot be trivially reversed.

From the tool's definition Reset all permissions for a specific package

Documented attack patterns abuse exactly the kind of access reset-permissions gives an agent:

How to control reset-permissions

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 reset-permissions:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "reset-permissions"
  ]
}

reset-permissions disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register ADB MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about reset-permissions

What does the reset-permissions tool do? +

Reset all permissions for a specific package. 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.

How do I enforce a policy on reset-permissions? +

Register the ADB MCP Server MCP server in PolicyLayer and add a rule for reset-permissions: 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.

What risk level is reset-permissions? +

reset-permissions is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit reset-permissions? +

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

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

reset-permissions 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.

Enforce policy on every ADB MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.