asc_add_beta_group_builds
Assign builds to a beta group via POST /v1/betaGroups/{id}/relationships/builds. Builds must be in VALID processingState; Apple rejects PROCESSING/FAILED/INVALID. For external groups, the first build to be distributed externally must clear beta review (handled by the beta-review sub-domain). Use ...
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-add-beta-group-builds.md
What asc_add_beta_group_builds does on Appstoreconnect Mcp
AI agents use asc_add_beta_group_builds 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.
Why asc_add_beta_group_builds is rated Medium
This tool creates or modifies data by assigning builds to beta groups, which affects TestFlight beta distribution. While not irreversible (builds can likely be removed), it enables distribution of application builds to testers, potentially impacting users and creating obligations.
From the tool's definition The tool description explicitly states it assigns builds to a beta group via POST request, creating a relationship between builds and beta groups. This is a write operation that modifies data (adds builds to beta group distributions).
Attacks that exploit this kind of access
The rule that runs asc_add_beta_group_builds 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_add_beta_group_builds, this is the rule to start with:
asc_add_beta_group_builds 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Appstoreconnect Mcp, apply this rule, and every asc_add_beta_group_builds call is checked against it from then on.
Questions about asc_add_beta_group_builds
Assign builds to a beta group via POST /v1/betaGroups/{id}/relationships/builds. Builds must be in VALID processingState; Apple rejects PROCESSING/FAILED/INVALID. For external groups, the first build to be distributed externally must clear beta review (handled by the beta-review sub-domain). Use asc_patch_build_beta_detail to control autoNotifyEnabled per 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.
Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_add_beta_group_builds: 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_add_beta_group_builds is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the asc_add_beta_group_builds 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_add_beta_group_builds. 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_add_beta_group_builds 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.
This server
Across the catalogue