asc_get_beta_feedback_crash_log
GET /v1/betaFeedbackCrashSubmissions/{id}/crashLog — returns the betaCrashLogs resource whose logText attribute is the full symbolicated-or-raw crash log. Logs can be large; output is capped at maxChars (default 200k) with a truncation note. Use after asc_list_beta_feedback_crash_submissions to d...
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-get-beta-feedback-crash-log.md
What asc_get_beta_feedback_crash_log does on Appstoreconnect Mcp
AI agents call asc_get_beta_feedback_crash_log 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_log is rated Low
This tool retrieves crash log data from App Store Connect without side effects. While the data retrieved (crash logs) could theoretically contain sensitive information about app internals, the operation itself is a read-only query.
From the tool's definition GET endpoint that 'returns the betaCrashLogs resource' with 'logText attribute'; described as 'drill into a specific crash' for inspection purposes with output capping; no modification, deletion, or external execution described.
Attacks that exploit this kind of access
The rule that runs asc_get_beta_feedback_crash_log 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_log, this is the rule to start with:
asc_get_beta_feedback_crash_log 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_log call is checked against it from then on.
Questions about asc_get_beta_feedback_crash_log
GET /v1/betaFeedbackCrashSubmissions/{id}/crashLog — returns the betaCrashLogs resource whose logText attribute is the full symbolicated-or-raw crash log. Logs can be large; output is capped at maxChars (default 200k) with a truncation note. Use after asc_list_beta_feedback_crash_submissions to drill into a specific crash. NOTE: Apple stores logs for a limited time — older submissions 404 here even though their metadata still lists (observed live on ~4-month-old submissions); the submission record itself remains readable. 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_log: 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_log 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_log 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_log. 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_log 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