Remove a tester from a beta group
AI agents call remove_tester_from_group to permanently remove resources in App Store Connect — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a tester from a beta group is a destructive action that revokes their access and membership. While it doesn't delete the tester account itself, the removal of the association is not easily reversible through this tool and constitutes an irreversible state change to group membership. Severity is medium because the blast radius is limited to beta testing access rather than production data or financial impact.
From the tool's definition 'Remove a tester from a beta group' — the word 'remove' indicates an irreversible deletion of the tester's association with the group
Documented attack patterns abuse exactly the kind of access remove_tester_from_group gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and App Store Connect, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_tester_from_group:
{
"version": "1",
"default": "deny",
"hide": [
"remove_tester_from_group"
]
} remove_tester_from_group disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a tester from a beta group. It is categorised as a Destructive tool in the App Store Connect MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the App Store Connect MCP server in PolicyLayer and add a rule for remove_tester_from_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 App Store Connect. Nothing to install.
remove_tester_from_group 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 remove_tester_from_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.
Set action: deny in the PolicyLayer policy for remove_tester_from_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.
remove_tester_from_group is provided by the App Store Connect MCP server (joshuarileydev/app-store-connect-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from App Store Connect, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
27 App Store Connect tools catalogued and risk-classified — across an index of 43,000+ MCP servers.