asc_delete_beta_app_localization
DELETE a BetaAppLocalization. The locale-specific copy is removed; testers in that locale fall back to whatever default TestFlight uses. Per-build
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-delete-beta-app-localization.md
What asc_delete_beta_app_localization does on Appstoreconnect Mcp
AI agents call asc_delete_beta_app_localization 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_beta_app_localization is rated Critical
This tool irreversibly deletes locale-specific TestFlight app copy. While the fallback mechanism means testers still see content, the operation cannot be undone and permanently removes customized localization data. This is a destructive modification of app metadata affecting the TestFlight beta testing experience, warranting the Destructive category over Write.
From the tool's definition DELETE a BetaAppLocalization... The locale-specific copy is removed
Attacks that exploit this kind of access
The rule that runs asc_delete_beta_app_localization 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_beta_app_localization, this is the rule to start with:
asc_delete_beta_app_localization 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_beta_app_localization call is checked against it from then on.
Questions about asc_delete_beta_app_localization
DELETE a BetaAppLocalization. The locale-specific copy is removed; testers in that locale fall back to whatever default TestFlight uses. Per-build. 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_beta_app_localization: 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_beta_app_localization 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_beta_app_localization 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_beta_app_localization. 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_beta_app_localization 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