asc_post_beta_recruitment_criterion

SERVERAppstoreconnect Mcp SOURCE@akoskomuves/appstoreconnect-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-beta-recruitment-criterion.md

WHAT IT DOES

What asc_post_beta_recruitment_criterion does on Appstoreconnect Mcp

AI agents use asc_post_beta_recruitment_criterion to create or update resources in Appstoreconnect Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appstoreconnect Mcp environment.

RISK

Why asc_post_beta_recruitment_criterion is rated Medium

This tool creates or modifies beta recruitment criteria that control who can auto-recruit into a beta group via a public link. While it affects beta testing access policies, it is reversible (can be patched or deleted as evidenced by sibling tools asc_delete_* and asc_patch_beta_group). The action does not delete data, execute arbitrary code, move money, or have irreversible destructive effects.

From the tool's definition POST /v1/betaRecruitmentCriteria — creates a new beta recruitment criterion; description states 'One criterion per group — if one already exists, PATCH it instead', indicating this tool creates or modifies data

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs asc_post_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_post_beta_recruitment_criterion, this is the rule to start with:

asc_post_beta_recruitment_criterion Rate-limited

asc_post_beta_recruitment_criterion stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "asc_post_beta_recruitment_criterion": {
      "limits": [
        {
          "counter": "asc_post_beta_recruitment_criterion_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Appstoreconnect Mcp, apply this rule, and every asc_post_beta_recruitment_criterion call is checked against it from then on.

FAQ

Questions about asc_post_beta_recruitment_criterion

What does the asc_post_beta_recruitment_criterion tool do? +

POST /v1/betaRecruitmentCriteria — gate public-link auto-recruitment on a beta group to devices matching the given device-family + OS-version windows. The group should be EXTERNAL with the public link enabled (see asc_patch_beta_group) for the criterion to have any effect. One criterion per group — if one already exists, PATCH it instead. Valid OS versions per family: asc_list_beta_recruitment_criterion_options. After creating, sanity-check with asc_get_beta_recruitment_compatible_build_check that matching devices can actually install a build. It is categorised as a Write tool in the Appstoreconnect Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on asc_post_beta_recruitment_criterion? +

Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_post_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.

What risk level is asc_post_beta_recruitment_criterion? +

asc_post_beta_recruitment_criterion is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit asc_post_beta_recruitment_criterion? +

Yes. Add a rate_limit block to the asc_post_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.

How do I block asc_post_beta_recruitment_criterion completely? +

Set action: deny in the PolicyLayer policy for asc_post_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.

What MCP server provides asc_post_beta_recruitment_criterion? +

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

KEEP EXPLORING

More on Appstoreconnect, and thousands of servers like it.

This server

All 278 Appstoreconnect tools →

Across the catalogue

team_manager_post_blackboard on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →