asc_delete_beta_recruitment_criterion
DELETE /v1/betaRecruitmentCriteria/{id} — remove the criterion entirely; the public link goes back to accepting ANY device. The beta group and its public link are untouched.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-delete-beta-recruitment-criterion.md
What asc_delete_beta_recruitment_criterion does on Appstoreconnect Mcp
AI agents call asc_delete_beta_recruitment_criterion 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_recruitment_criterion is rated Critical
This tool permanently deletes beta recruitment criteria configuration. While the deletion itself is reversible in the sense that criteria could be re-added, the operation is irreversible in nature (cannot be undone as a single action) and modifies app distribution settings. The blast radius is significant as it affects TestFlight beta recruitment by removing enrollment restrictions.
From the tool's definition 'DELETE /v1/betaRecruitmentCriteria/{id} — remove the criterion entirely' - the tool explicitly performs a DELETE operation that irreversibly removes beta recruitment criteria
Attacks that exploit this kind of access
The rule that runs asc_delete_beta_recruitment_criterion 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_delete_beta_recruitment_criterion, this is the rule to start with:
asc_delete_beta_recruitment_criterion 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_delete_beta_recruitment_criterion call is checked against it from then on.
Questions about asc_delete_beta_recruitment_criterion
DELETE /v1/betaRecruitmentCriteria/{id} — remove the criterion entirely; the public link goes back to accepting ANY device. The beta group and its public link are untouched. 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_delete_beta_recruitment_criterion: 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_delete_beta_recruitment_criterion 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_delete_beta_recruitment_criterion 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_delete_beta_recruitment_criterion. 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_delete_beta_recruitment_criterion 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