asc_delete_webhook
DELETE /v1/webhooks/{id} — permanently remove the webhook and stop all deliveries. Delivery history is gone with it. To pause instead of delete, PATCH enabled=false.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-delete-webhook.md
What asc_delete_webhook does on Appstoreconnect Mcp
AI agents call asc_delete_webhook 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_webhook is rated Critical
This tool permanently deletes a webhook resource and its associated delivery history with no undo capability. While the blast radius is limited to webhook configuration rather than user data or financial systems, the irreversible nature and explicit mention of permanent removal and data loss clearly place it in the Destructive category.
From the tool's definition Tool description explicitly states 'permanently remove the webhook' and 'Delivery history is gone with it.' The DELETE operation is irreversible and data (delivery history) cannot be recovered.
Attacks that exploit this kind of access
The rule that runs asc_delete_webhook 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_webhook, this is the rule to start with:
asc_delete_webhook 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_webhook call is checked against it from then on.
Questions about asc_delete_webhook
DELETE /v1/webhooks/{id} — permanently remove the webhook and stop all deliveries. Delivery history is gone with it. To pause instead of delete, PATCH enabled=false. 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_webhook: 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_webhook 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_webhook 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_webhook. 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_webhook 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