asc_list_beta_app_review_details
List BetaAppReviewDetail records. Filter by appId to scope to one app (typically returns one record per app). The detail record persists across builds — same contact info + demo account + notes are reused for every submission unless you patch it.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-list-beta-app-review-details.md
What asc_list_beta_app_review_details does on Appstoreconnect Mcp
AI agents call asc_list_beta_app_review_details 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_details is rated Low
This tool retrieves and queries beta app review detail records from App Store Connect without any side effects. It only filters and returns existing data about review details (contact info, demo account notes) that persist across builds. No data is created, modified, deleted, or executed.
From the tool's definition Tool name begins with 'list' and description states 'List BetaAppReviewDetail records' with filtering capability. No modification, deletion, or execution actions are performed.
Attacks that exploit this kind of access
The rule that runs asc_list_beta_app_review_details 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_details, this is the rule to start with:
asc_list_beta_app_review_details 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_details call is checked against it from then on.
Questions about asc_list_beta_app_review_details
List BetaAppReviewDetail records. Filter by appId to scope to one app (typically returns one record per app). The detail record persists across builds — same contact info + demo account + notes are reused for every submission unless you patch it. 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_details: 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_details 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_details 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_details. 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_details 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