asc_delete_beta_group

DELETE a beta group. Apple supports DELETE on this resource (unlike offer codes). All tester + build linkages are removed atomically. Testers themselves are NOT deleted — they remain as BetaTester records, just unassigned from this group. Builds are NOT affected.

SERVERAppstoreconnect Mcp SOURCE@akoskomuves/appstoreconnect-mcp
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/io-github-akoskomuves-appstoreconnect-mcp/asc-delete-beta-group.md

What asc_delete_beta_group does on Appstoreconnect Mcp

AI agents call asc_delete_beta_group 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_group is rated Critical

This tool deletes a beta group and permanently removes all associated tester and build linkages. While the testers and builds themselves remain in the system (unaffected), the beta group record and its relationships are irreversibly destroyed. This fits the Destructive category as it performs an action that cannot be undone.

From the tool's definition The tool description explicitly states "DELETE a beta group" and "All tester + build linkages are removed atomically." This is an irreversible deletion operation that cannot be undone.

Questions about asc_delete_beta_group

What does the asc_delete_beta_group tool do? +

DELETE a beta group. Apple supports DELETE on this resource (unlike offer codes). All tester + build linkages are removed atomically. Testers themselves are NOT deleted — they remain as BetaTester records, just unassigned from this group. Builds are NOT affected. 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.

How do I enforce a policy on asc_delete_beta_group? +

Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_delete_beta_group: 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.

What risk level is asc_delete_beta_group? +

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

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

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

asc_delete_beta_group 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Appstoreconnect's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.