Delete a webhook subscription and stop all future webhooks to its endpoint
AI agents call delete_webhook_subscription to permanently remove resources in Shopify Graphql — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes a webhook subscription configuration, which is irreversible and cannot be undone without manually recreating it. While this doesn't delete data directly, it destroys infrastructure configuration in the Shopify store.
From the tool's definition delete_webhook_subscription: Delete a webhook subscription and stop all future webhooks to its endpoint
Attacks that exploit this kind of access
Delete a webhook subscription and stop all future webhooks to its endpoint. It is categorised as a Destructive tool in the Shopify Graphql MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Shopify Graphql MCP server in PolicyLayer and add a rule for delete_webhook_subscription: 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 Shopify Graphql. Nothing to install.
delete_webhook_subscription 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 delete_webhook_subscription 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 delete_webhook_subscription. 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.
delete_webhook_subscription is provided by the Shopify Graphql MCP server (uvu-store/shopify-graphql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →