asc_post_beta_tester

Create a BetaTester record from an email. Apple uses the email as the uniqueness key per team; a duplicate email surfaces as an API error verbatim.

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-tester.md

What asc_post_beta_tester does on Appstoreconnect Mcp

AI agents use asc_post_beta_tester 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_post_beta_tester is rated Medium

This tool performs a create operation that adds a new beta tester to the App Store Connect system. It results in reversible data modification (the tester can be removed). While it involves user management for a commercial app platform, it does not move money (Financial), execute arbitrary code (Execute), or permanently destroy data (Destructive).

From the tool's definition Tool creates a new BetaTester record from email, as stated: 'Create a BetaTester record from an email'. This is a create operation that modifies data reversibly.

Questions about asc_post_beta_tester

What does the asc_post_beta_tester tool do? +

Create a BetaTester record from an email. Apple uses the email as the uniqueness key per team; a duplicate email surfaces as an API error verbatim. 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_tester? +

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

asc_post_beta_tester 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_tester? +

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

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

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