asc_get_beta_feedback_crash_submission
Fetch one crash feedback submission with full device context. include=build,tester for triage context. This returns the submission METADATA only — for the crash log text itself use asc_get_beta_feedback_crash_log.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-get-beta-feedback-crash-submission.md
What asc_get_beta_feedback_crash_submission does on Appstoreconnect Mcp
AI agents call asc_get_beta_feedback_crash_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_feedback_crash_submission is rated Low
This tool retrieves beta crash feedback metadata and device context information from App Store Connect. It performs a read-only query operation with no side effects—no data is created, modified, deleted, or financial operations performed. The explicit mention of returning 'METADATA only' reinforces that this is a passive data retrieval operation.
From the tool's definition Tool description states 'Fetch one crash feedback submission' and 'returns the submission METADATA only', indicating retrieval of data without modification or deletion.
Attacks that exploit this kind of access
The rule that runs asc_get_beta_feedback_crash_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_feedback_crash_submission, this is the rule to start with:
asc_get_beta_feedback_crash_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_feedback_crash_submission call is checked against it from then on.
Questions about asc_get_beta_feedback_crash_submission
Fetch one crash feedback submission with full device context. include=build,tester for triage context. This returns the submission METADATA only — for the crash log text itself use asc_get_beta_feedback_crash_log. 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_feedback_crash_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_feedback_crash_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_feedback_crash_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_feedback_crash_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_feedback_crash_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