asc_post_beta_tester_invitation
Send (or resend) the TestFlight invite email for a tester on a specific app. Required: appId.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-beta-tester-invitation.md
What asc_post_beta_tester_invitation does on Appstoreconnect Mcp
AI agents use asc_post_beta_tester_invitation 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_invitation is rated Medium
This tool sends or resends a TestFlight invitation email, which modifies tester invitation records and triggers an email communication. While it doesn't create new testers or delete data, it actively writes/modifies invitation state. The severity is medium because misuse could spam testers with unwanted invitations or cause operational disruption, but it's reversible and doesn't destroy data or move money.
From the tool's definition Tool description states 'Send (or resend) the TestFlight invite email' which is a write operation that creates/modifies the state of tester invitations in App Store Connect.
Attacks that exploit this kind of access
The rule that runs asc_post_beta_tester_invitation 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_tester_invitation, this is the rule to start with:
asc_post_beta_tester_invitation 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_post_beta_tester_invitation call is checked against it from then on.
Questions about asc_post_beta_tester_invitation
Send (or resend) the TestFlight invite email for a tester on a specific app. Required: appId. 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_post_beta_tester_invitation: 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_post_beta_tester_invitation 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_post_beta_tester_invitation 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_post_beta_tester_invitation. 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_post_beta_tester_invitation 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