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

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

Questions about asc_remove_beta_group_testers

What does the asc_remove_beta_group_testers tool do? +

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.

How do I enforce a policy on asc_remove_beta_group_testers? +

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.

What risk level is asc_remove_beta_group_testers? +

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.

Can I rate-limit asc_remove_beta_group_testers? +

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.

How do I block asc_remove_beta_group_testers completely? +

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.

What MCP server provides asc_remove_beta_group_testers? +

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.

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