This record as markdown: /tools/alexgladkov-claude-in-mobile/rustore-discard.md
What rustore_discard does on Claude Mobile
AI agents call rustore_discard 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.
Why rustore_discard is rated Critical
This tool permanently deletes a version draft from RuStore (a Russian app store), which is an irreversible operation. Deletion cannot be undone, fitting the Destructive category. The severity is high because an AI agent misusing this could destroy in-progress app store submissions or drafts, disrupting the app publishing workflow.
From the tool's definition Tool name 'rustore_discard' combined with description 'Delete RuStore version draft' explicitly indicates irreversible deletion of draft data.
Attacks that exploit this kind of access
The rule that runs rustore_discard 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 rustore_discard, this is the rule to start with:
rustore_discard is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every rustore_discard call is checked against it from then on.
Questions about rustore_discard
Delete RuStore version draft. 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.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for rustore_discard: 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.
rustore_discard 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 rustore_discard 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 rustore_discard. 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.
rustore_discard 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.
More on Claude Mobile, and thousands of servers like it.
Across the catalogue