permission_reset

Reset all permissions for an app

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexgladkov-claude-in-mobile/permission-reset.md

WHAT IT DOES

What permission_reset does on Claude Mobile

AI agents call permission_reset to permanently remove resources in Claude Mobile, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why permission_reset is rated Critical

Resetting all permissions for an app permanently removes all previously granted permission states, which is a destructive action. Users/apps would need to manually re-grant each permission, and any workflows depending on those permissions would break. This cannot be automatically undone, making it Destructive with high severity due to the potential to disrupt app functionality across all its permissions at once.

From the tool's definition 'Reset all permissions for an app' — resetting permissions is irreversible in the sense that all previously granted permissions are wiped and cannot be automatically restored

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs permission_reset safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For permission_reset, this is the rule to start with:

permission_reset Hidden

permission_reset is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "permission_reset"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every permission_reset call is checked against it from then on.

FAQ

Questions about permission_reset

What does the permission_reset tool do? +

Reset all permissions for an app. It is categorised as a Destructive tool in the Claude Mobile 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 permission_reset? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for permission_reset: 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 Claude Mobile. Nothing to install.

What risk level is permission_reset? +

permission_reset 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 permission_reset? +

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

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

permission_reset is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Mobile, and thousands of servers like it.

This server

All 198 Claude Mobile tools → Critical-risk tools on this server →

Across the catalogue

team_manager_reset on Team Manager MCP →reset_mcp_runtime_metrics on 0xpdf → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →