asc_remove_beta_group_testers
Remove testers from a beta group via DELETE /v1/betaGroups/{id}/relationships/betaTesters. Pass only the IDs you want removed — Apple uses the body, not a
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-remove-beta-group-testers.md
What asc_remove_beta_group_testers does on Appstoreconnect Mcp
AI agents call asc_remove_beta_group_testers 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_testers is rated Critical
This tool performs a DELETE operation to remove testers from a beta group. The removal is irreversible in the sense that the relationship is destroyed and would need to be explicitly re-added. This fits the Destructive category as it permanently removes associations between testers and beta groups.
From the tool's definition Remove testers from a beta group via DELETE /v1/betaGroups/{id}/relationships/betaTesters
Attacks that exploit this kind of access
The rule that runs asc_remove_beta_group_testers 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_testers, this is the rule to start with:
asc_remove_beta_group_testers 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_testers call is checked against it from then on.
Questions about asc_remove_beta_group_testers
Remove testers from a beta group via DELETE /v1/betaGroups/{id}/relationships/betaTesters. Pass only the IDs you want removed — Apple uses the body, not a. 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_testers: 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_testers 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_testers 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_testers. 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_testers 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