asc_get_beta_app_review_submission
Fetch a single BetaAppReviewSubmission with the build relationship expanded. Use to check current betaReviewState — APPROVED unlocks external distribution, REJECTED requires re-submission after fixes.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-get-beta-app-review-submission.md
What asc_get_beta_app_review_submission does on Appstoreconnect Mcp
AI agents call asc_get_beta_app_review_submission 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_get_beta_app_review_submission is rated Low
This tool retrieves information about the current state of a beta app review submission (checking betaReviewState). It has no side effects, does not create, modify, delete, or execute operations. It is purely a data retrieval operation that queries the existing state of an app review submission for informational purposes.
From the tool's definition Tool name uses 'get' and description states 'Fetch a single BetaAppReviewSubmission' with relationship expanded. The operation retrieves data about beta app review submission status without modifying or deleting anything.
Attacks that exploit this kind of access
The rule that runs asc_get_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_get_beta_app_review_submission, this is the rule to start with:
asc_get_beta_app_review_submission 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_get_beta_app_review_submission call is checked against it from then on.
Questions about asc_get_beta_app_review_submission
Fetch a single BetaAppReviewSubmission with the build relationship expanded. Use to check current betaReviewState — APPROVED unlocks external distribution, REJECTED requires re-submission after fixes. 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_get_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_get_beta_app_review_submission 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_get_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_get_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_get_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.
This server
Across the catalogue