This record as markdown: /tools/uvu-store-shopify-graphql-mcp/delete-menu.md
What delete_menu does on Shopify Graphql
AI agents call delete_menu 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.
Why delete_menu is rated Critical
This tool permanently removes navigation menus from a Shopify store, which cannot be undone and constitutes data destruction. While the blast radius is limited to store navigation UI (not customer data or financial records), the irreversible nature and potential to disrupt store functionality elevates this to Destructive rather than Write.
From the tool's definition Tool name 'delete_menu' with description 'Delete a navigation menu' explicitly performs an irreversible deletion operation on store configuration data.
Attacks that exploit this kind of access
The rule that runs delete_menu safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Shopify Graphql, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_menu, this is the rule to start with:
delete_menu 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 Shopify Graphql, apply this rule, and every delete_menu call is checked against it from then on.
Questions about delete_menu
Delete a navigation menu. 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_menu: 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_menu 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_menu 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_menu. 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_menu 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.
More on Shopify Graphql, and thousands of servers like it.
Across the catalogue