Delete a marketing event
AI agents call delete_marketing_event 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.
This tool permanently removes a marketing event from the Shopify store. Deletion is an irreversible action with no undo capability. While the blast radius is limited to marketing events (not financial transactions or store operations), unauthorized or accidental deletion could disrupt marketing campaigns and cause data loss.
From the tool's definition Tool name 'delete_marketing_event' with description 'Delete a marketing event' indicates irreversible removal of data. The verb 'delete' explicitly signals a destructive operation that cannot be undone.
Attacks that exploit this kind of access
Delete a marketing event. 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_marketing_event: 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_marketing_event 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_marketing_event 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_marketing_event. 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_marketing_event 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 →