asc_remove_beta_group_builds
Unassign builds from a beta group via DELETE /v1/betaGroups/{id}/relationships/builds. The build itself is not deleted; only the group→build linkage is removed. Testers in the group lose visibility of these builds in TestFlight.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-remove-beta-group-builds.md
What asc_remove_beta_group_builds does on Appstoreconnect Mcp
AI agents call asc_remove_beta_group_builds 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_remove_beta_group_builds is rated Critical
Although the build itself is not deleted, the relationship removal is performed via a DELETE operation and causes testers to lose access to builds in TestFlight. This is a non-trivial side effect that removes an existing association and cannot easily be undone (testers lose visibility).
From the tool's definition Unassign builds from a beta group via DELETE /v1/betaGroups/{id}/relationships/builds. Testers in the group lose visibility of these builds in TestFlight.
Attacks that exploit this kind of access
The rule that runs asc_remove_beta_group_builds 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_remove_beta_group_builds, this is the rule to start with:
asc_remove_beta_group_builds 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_remove_beta_group_builds call is checked against it from then on.
Questions about asc_remove_beta_group_builds
Unassign builds from a beta group via DELETE /v1/betaGroups/{id}/relationships/builds. The build itself is not deleted; only the group→build linkage is removed. Testers in the group lose visibility of these builds in TestFlight. 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_remove_beta_group_builds: 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_remove_beta_group_builds 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_remove_beta_group_builds 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_remove_beta_group_builds. 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_remove_beta_group_builds 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