Delete a pixel
AI agents call delete_pixel 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 pixel from the Shopify store, which cannot be undone and is a destructive action. While pixels are not financial data, their deletion cannot be easily recovered and affects store analytics/tracking configuration. Destructive is the appropriate category as it represents an irreversible data deletion operation.
From the tool's definition Tool name is 'delete_pixel' and description states 'Delete a pixel'. The verb 'delete' combined with an irreversible operation on a tracking/analytics pixel indicates permanent removal of data/configuration.
Attacks that exploit this kind of access
Delete a pixel. 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_pixel: 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_pixel 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_pixel 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_pixel. 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_pixel 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 →