permission_revoke

Revoke app permission

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-revoke.md

WHAT IT DOES

What permission_revoke does on Claude Mobile

AI agents call permission_revoke 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_revoke is rated Critical

Revoking a permission is a destructive action: it removes an app's granted access right (e.g., camera, location, contacts). While technically a permission can be re-granted, the act of revocation itself is a one-way destructive operation that removes existing state. Misuse by an AI agent could break app functionality or deny access to critical device resources.

From the tool's definition 'Revoke app permission' - revoking a permission removes an access right from an app, which can break functionality and is not automatically reversible without re-granting

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs permission_revoke 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_revoke, this is the rule to start with:

permission_revoke Hidden

permission_revoke 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_revoke"
  ]
}

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_revoke call is checked against it from then on.

FAQ

Questions about permission_revoke

What does the permission_revoke tool do? +

Revoke app permission. 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_revoke? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for permission_revoke: 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_revoke? +

permission_revoke 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_revoke? +

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

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

permission_revoke 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

web3_revoke_key on 0xarchive →revoke_api_token on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →