Delete a metaobject entry.
AI agents call delete_metaobject to permanently remove resources in AdminAgent — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (a metaobject entry) that cannot be recovered without external backups. While not directly financial, the loss of metaobject data could impact store operations, product information, or custom business logic depending on what the metaobject contained.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a metaobject entry.' Metaobjects in Shopify are custom data structures that store structured data for products, collections, and other resources. Deletion is irreversible.
Attacks that exploit this kind of access
Delete a metaobject entry. It is categorised as a Destructive tool in the AdminAgent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AdminAgent MCP server in PolicyLayer and add a rule for delete_metaobject: 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 AdminAgent. Nothing to install.
delete_metaobject 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_metaobject 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_metaobject. 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_metaobject is provided by the AdminAgent MCP server (rushikeshmore/admin-agent). 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 →