list_metafield_definitions
AI agents call list_metafield_definitions to retrieve information from AdminAgent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_' prefix is a clear indicator of a read-only operation that queries and retrieves data. In the context of an AdminAgent managing Shopify stores, listing metafield definitions is a non-destructive information retrieval operation. No side effects, modifications, or deletions are implied. Confidence is slightly reduced due to the empty description, but the naming convention is unambiguous.
From the tool's definition Tool name 'list_metafield_definitions' uses the 'list' verb, indicating data retrieval. Description is empty, but the name and context of a Shopify Admin tool strongly suggest this retrieves metadata definitions without modification.
Attacks that exploit this kind of access
list_metafield_definitions. It is categorised as a Read tool in the AdminAgent MCP Server, which means it retrieves data without modifying state.
Register the AdminAgent MCP server in PolicyLayer and add a rule for list_metafield_definitions: 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.
list_metafield_definitions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_metafield_definitions 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 list_metafield_definitions. 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.
list_metafield_definitions 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 →