asc_delete_beta_feedback_crash_submission

DELETE /v1/betaFeedbackCrashSubmissions/{id}. Permanently removes the crash feedback record (including its crash log) from App Store Connect. Irreversible; the tester is not notified.

SERVERAppstoreconnect Mcp SOURCE@akoskomuves/appstoreconnect-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-delete-beta-feedback-crash-submission.md

WHAT IT DOES

What asc_delete_beta_feedback_crash_submission does on Appstoreconnect Mcp

AI agents call asc_delete_beta_feedback_crash_submission to permanently remove resources in Appstoreconnect Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why asc_delete_beta_feedback_crash_submission is rated Critical

The tool permanently deletes crash feedback records and logs from App Store Connect with no undo capability. This is an irreversible destructive operation that removes data. While the blast radius is limited to test feedback data rather than production systems, the permanent loss of debugging information and crash logs constitutes a high-severity destructive action.

From the tool's definition DELETE /v1/betaFeedbackCrashSubmissions/{id}. Permanently removes the crash feedback record (including its crash log) from App Store Connect. Irreversible

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs asc_delete_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_delete_beta_feedback_crash_submission, this is the rule to start with:

asc_delete_beta_feedback_crash_submission Hidden

asc_delete_beta_feedback_crash_submission is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "asc_delete_beta_feedback_crash_submission"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Appstoreconnect Mcp, apply this rule, and every asc_delete_beta_feedback_crash_submission call is checked against it from then on.

FAQ

Questions about asc_delete_beta_feedback_crash_submission

What does the asc_delete_beta_feedback_crash_submission tool do? +

DELETE /v1/betaFeedbackCrashSubmissions/{id}. Permanently removes the crash feedback record (including its crash log) from App Store Connect. Irreversible; the tester is not notified. It is categorised as a Destructive tool in the Appstoreconnect Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on asc_delete_beta_feedback_crash_submission? +

Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_delete_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.

What risk level is asc_delete_beta_feedback_crash_submission? +

asc_delete_beta_feedback_crash_submission is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit asc_delete_beta_feedback_crash_submission? +

Yes. Add a rate_limit block to the asc_delete_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.

How do I block asc_delete_beta_feedback_crash_submission completely? +

Set action: deny in the PolicyLayer policy for asc_delete_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.

What MCP server provides asc_delete_beta_feedback_crash_submission? +

asc_delete_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.

KEEP EXPLORING

More on Appstoreconnect, and thousands of servers like it.

This server

All 278 Appstoreconnect tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →