asc_post_beta_app_review_submission
Submit a build for Apple beta review. Required: buildId. The body has NO attributes — only the build relationship. Once submitted, betaReviewState walks WAITING_FOR_REVIEW → IN_REVIEW → APPROVED (or REJECTED), typically over 24-48h.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-beta-app-review-submission.md
What asc_post_beta_app_review_submission does on Appstoreconnect Mcp
AI agents invoke asc_post_beta_app_review_submission to trigger actions in Appstoreconnect Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why asc_post_beta_app_review_submission is rated High
This tool triggers an external operation (submitting a build to Apple's review process) that has real-world consequences with external parties. It initiates a review workflow that cannot be simply undone once submitted, and involves official Apple review processes. This qualifies as Execute due to triggering an external operation with significant downstream effects.
From the tool's definition Submit a build for Apple beta review... Once submitted, betaReviewState walks WAITING_FOR_REVIEW → IN_REVIEW → APPROVED (or REJECTED)
Attacks that exploit this kind of access
The rule that runs asc_post_beta_app_review_submission 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_app_review_submission, this is the rule to start with:
asc_post_beta_app_review_submission stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_app_review_submission call is checked against it from then on.
Questions about asc_post_beta_app_review_submission
Submit a build for Apple beta review. Required: buildId. The body has NO attributes — only the build relationship. Once submitted, betaReviewState walks WAITING_FOR_REVIEW → IN_REVIEW → APPROVED (or REJECTED), typically over 24-48h. It is categorised as a Execute tool in the Appstoreconnect Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_post_beta_app_review_submission: 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_app_review_submission is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the asc_post_beta_app_review_submission 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_app_review_submission. 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_app_review_submission 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.
Across the catalogue