Get metafields for any resource (product, order, customer, etc.).
AI agents call get_metafields 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 tool retrieves metafield data from Shopify resources (products, orders, customers, etc.) without creating, modifying, or deleting anything. It is a read-only query operation with no side effects. Even though the broader server enables destructive operations (cancel_order, cancel_fulfillment), this specific tool is clearly a data retrieval function, placing it in the Read category with low severity.
From the tool's definition Tool name 'get_metafields' and description 'Get metafields' indicate a retrieval operation with no modification of data.
Attacks that exploit this kind of access
Get metafields for any resource (product, order, customer, etc.). 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 get_metafields: 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.
get_metafields 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 get_metafields 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 get_metafields. 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.
get_metafields 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 →