asc_delete_app_store_version
DELETE an App Store version. Allowed only when the version is in an editable state (PREPARE_FOR_SUBMISSION, *_REJECTED, INVALID_BINARY, DEVELOPER_REMOVED_FROM_SALE). The tool pre-checks the state with one GET and refuses client-side for frozen states (under review) or live states (READY_FOR_SALE ...
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-delete-app-store-version.md
What asc_delete_app_store_version does on Appstoreconnect Mcp
AI agents call asc_delete_app_store_version to permanently remove resources in Appstoreconnect Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why asc_delete_app_store_version is rated Critical
This tool permanently deletes an App Store version, which is an irreversible operation that destroys data and configuration. While the tool includes safeguards to prevent deletion of live versions (READY_FOR_SALE) or versions under review, it still allows deletion of versions in editable states. Deletion of an app version—even in a preparatory state—cannot be undone and represents data destruction.
From the tool's definition The tool name contains 'delete' and the description explicitly states 'DELETE an App Store version.' The description confirms this is an irreversible operation: 'DELETE an App Store version.'
Attacks that exploit this kind of access
The rule that runs asc_delete_app_store_version safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appstoreconnect Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For asc_delete_app_store_version, this is the rule to start with:
asc_delete_app_store_version 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 Appstoreconnect Mcp, apply this rule, and every asc_delete_app_store_version call is checked against it from then on.
Questions about asc_delete_app_store_version
DELETE an App Store version. Allowed only when the version is in an editable state (PREPARE_FOR_SUBMISSION, *_REJECTED, INVALID_BINARY, DEVELOPER_REMOVED_FROM_SALE). The tool pre-checks the state with one GET and refuses client-side for frozen states (under review) or live states (READY_FOR_SALE — would orphan customers; release-pending — Apple rejects). It is categorised as a Destructive tool in the Appstoreconnect Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_delete_app_store_version: 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 Appstoreconnect Mcp. Nothing to install.
asc_delete_app_store_version 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 asc_delete_app_store_version 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 asc_delete_app_store_version. 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.
asc_delete_app_store_version is provided by the Appstoreconnect MCP server (@akoskomuves/appstoreconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appstoreconnect, and thousands of servers like it.
Across the catalogue