Submit a customer data erasure request (GDPR right to be forgotten)
AI agents call request_customer_data_erasure 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.
A data erasure request permanently deletes customer personal data in compliance with GDPR. This action is irreversible — once customer data is erased, it cannot be recovered. The 'right to be forgotten' explicitly implies permanent removal, making this a Destructive action with critical severity given the potential for irreversible loss of customer records across a Shopify store.
From the tool's definition Submit a customer data erasure request (GDPR right to be forgotten)
Attacks that exploit this kind of access
Submit a customer data erasure request (GDPR right to be forgotten). 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 request_customer_data_erasure: 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.
request_customer_data_erasure 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 request_customer_data_erasure 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 request_customer_data_erasure. 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.
request_customer_data_erasure 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 →