asc_delete_customer_review_response
DELETE /v1/customerReviewResponses/{id} — remove your public reply from the App Store. The review itself is untouched (customer reviews cannot be deleted by developers). Get the response ID from asc_get_customer_review_response or the list digest.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-delete-customer-review-response.md
What asc_delete_customer_review_response does on Appstoreconnect Mcp
AI agents call asc_delete_customer_review_response 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.
Why asc_delete_customer_review_response is rated Critical
This tool permanently removes published content (a developer's reply to a customer review) from a public platform without reversal. While not as damaging as deleting the review itself or app data, deleting a public response cannot be undone and affects the app's public reputation and customer communication record. This meets the Destructive category definition: irreversibly deletes data that cannot be undone.
From the tool's definition Tool name contains 'delete' and description explicitly states 'remove your public reply from the App Store' — an irreversible action.
Attacks that exploit this kind of access
The rule that runs asc_delete_customer_review_response 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_customer_review_response, this is the rule to start with:
asc_delete_customer_review_response is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Appstoreconnect Mcp, apply this rule, and every asc_delete_customer_review_response call is checked against it from then on.
Questions about asc_delete_customer_review_response
DELETE /v1/customerReviewResponses/{id} — remove your public reply from the App Store. The review itself is untouched (customer reviews cannot be deleted by developers). Get the response ID from asc_get_customer_review_response or the list digest. 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.
Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_delete_customer_review_response: 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_delete_customer_review_response is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the asc_delete_customer_review_response 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_delete_customer_review_response. 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_delete_customer_review_response 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.
Across the catalogue