asc_list_beta_app_review_submissions
List beta-app-review submissions across the team, with the optional buildId filter to narrow to a single build
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-list-beta-app-review-submissions.md
What asc_list_beta_app_review_submissions does on Appstoreconnect Mcp
AI agents call asc_list_beta_app_review_submissions 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_list_beta_app_review_submissions is rated Low
This tool retrieves and queries beta app review submission data with an optional filter parameter. It has no side effects—it only reads information about review submissions across the team. This is a straightforward Read operation with minimal risk; the worst case is exposure of information about app reviews already submitted to Apple's review process.
From the tool's definition Tool name uses 'list' verb and description states 'List beta-app-review submissions' with optional filtering; no modification, deletion, or execution described.
Attacks that exploit this kind of access
The rule that runs asc_list_beta_app_review_submissions 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_list_beta_app_review_submissions, this is the rule to start with:
asc_list_beta_app_review_submissions 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_list_beta_app_review_submissions call is checked against it from then on.
Questions about asc_list_beta_app_review_submissions
List beta-app-review submissions across the team, with the optional buildId filter to narrow to a single build. 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_list_beta_app_review_submissions: 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_list_beta_app_review_submissions 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_list_beta_app_review_submissions 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_list_beta_app_review_submissions. 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_list_beta_app_review_submissions 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