asc_add_beta_group_testers

Add existing BetaTester records to a beta group via POST /v1/betaGroups/{id}/relationships/betaTesters. Pass tester IDs (NOT emails — use asc_post_beta_tester to look up or create from an email). Idempotent on the wire (re-adding a member is a no-op). Apple does not push a fresh invite email on r...

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-add-beta-group-testers.md

What asc_add_beta_group_testers does on Appstoreconnect Mcp

AI agents use asc_add_beta_group_testers 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_testers is rated Medium

The tool modifies the state of a beta group by associating beta testers with it via a POST operation. This is a write operation that creates new relationships/associations in App Store Connect. While reversible (testers can be removed), it affects application testing workflow and permissions.

From the tool's definition POST /v1/betaGroups/{id}/relationships/betaTesters indicates the tool creates or modifies beta group membership relationships by adding tester records.

Questions about asc_add_beta_group_testers

What does the asc_add_beta_group_testers tool do? +

Add existing BetaTester records to a beta group via POST /v1/betaGroups/{id}/relationships/betaTesters. Pass tester IDs (NOT emails — use asc_post_beta_tester to look up or create from an email). Idempotent on the wire (re-adding a member is a no-op). Apple does not push a fresh invite email on re-add. 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_add_beta_group_testers? +

Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_add_beta_group_testers: 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_add_beta_group_testers? +

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

Can I rate-limit asc_add_beta_group_testers? +

Yes. Add a rate_limit block to the asc_add_beta_group_testers 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_add_beta_group_testers completely? +

Set action: deny in the PolicyLayer policy for asc_add_beta_group_testers. 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_add_beta_group_testers? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Appstoreconnect's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.