asc_list_beta_feedback_crash_submissions
List crash feedback testers agreed to share from TestFlight via GET /v1/apps/{id}/betaFeedbackCrashSubmissions. Same filters as the screenshot list (build, tester, device, OS, platform). Each record has a crashLog relationship — pull the log text with asc_get_beta_feedback_crash_log. Read-only re...
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-list-beta-feedback-crash-submissions.md
What asc_list_beta_feedback_crash_submissions does on Appstoreconnect Mcp
AI agents call asc_list_beta_feedback_crash_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_feedback_crash_submissions is rated Low
This tool performs a query/list operation on crash feedback data from TestFlight. It uses HTTP GET, supports filtering parameters (build, tester, device, OS, platform), and is explicitly marked as read-only. There are no side effects, data modifications, deletions, or external state changes.
From the tool's definition Tool description explicitly states 'List crash feedback' via GET request and 'Read-only resource'. The operation retrieves TestFlight crash submission data without modifying or deleting it.
Attacks that exploit this kind of access
The rule that runs asc_list_beta_feedback_crash_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_feedback_crash_submissions, this is the rule to start with:
asc_list_beta_feedback_crash_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_feedback_crash_submissions call is checked against it from then on.
Questions about asc_list_beta_feedback_crash_submissions
List crash feedback testers agreed to share from TestFlight via GET /v1/apps/{id}/betaFeedbackCrashSubmissions. Same filters as the screenshot list (build, tester, device, OS, platform). Each record has a crashLog relationship — pull the log text with asc_get_beta_feedback_crash_log. Read-only resource. 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_feedback_crash_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_feedback_crash_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_feedback_crash_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_feedback_crash_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_feedback_crash_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