asc_list_beta_groups
List beta groups. Pass appId to scope to a single app (the common case). Each row shows name, kind (INT/EXT), tester-count via the betaTesters relationship if requested, public-link state, and ID. Use to find a group before assigning a build or inviting testers.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-list-beta-groups.md
What asc_list_beta_groups does on Appstoreconnect Mcp
AI agents call asc_list_beta_groups to retrieve information from Appstoreconnect Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why asc_list_beta_groups is rated Low
This tool retrieves and queries beta group information without side effects. It enables discovery of groups for subsequent actions but does not itself modify data, execute code, or perform destructive operations. The blast radius of misuse is limited to information disclosure about beta testing infrastructure.
From the tool's definition Tool name 'asc_list_beta_groups' and description explicitly states 'List beta groups' with details about retrieving name, kind, tester-count, public-link state, and ID. No modification, deletion, or execution implied—purely data retrieval.
Attacks that exploit this kind of access
The rule that runs asc_list_beta_groups 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_list_beta_groups, this is the rule to start with:
asc_list_beta_groups is read-only, so it stays allowed. 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_list_beta_groups call is checked against it from then on.
Questions about asc_list_beta_groups
List beta groups. Pass appId to scope to a single app (the common case). Each row shows name, kind (INT/EXT), tester-count via the betaTesters relationship if requested, public-link state, and ID. Use to find a group before assigning a build or inviting testers. It is categorised as a Read tool in the Appstoreconnect Mcp MCP Server, which means it retrieves data without modifying state.
Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_list_beta_groups: 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_list_beta_groups is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the asc_list_beta_groups 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_list_beta_groups. 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_list_beta_groups 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