create_metaobject
AI agents use create_metaobject to create or update resources in AdminAgent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AdminAgent environment.
The 'create_' prefix unambiguously indicates object creation, which is a reversible Write operation. In Shopify, metaobjects are custom data structures; creating them modifies the store's data model but is reversible via deletion. High severity assigned due to potential bulk scope (admin context) and Shopify integration.
From the tool's definition Tool name 'create_metaobject' indicates creation of data via 'create' verb. Empty description limits certainty.
Attacks that exploit this kind of access
create_metaobject. It is categorised as a Write tool in the AdminAgent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AdminAgent MCP server in PolicyLayer and add a rule for create_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.
create_metaobject is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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 →