run_shopifyql
AI agents invoke run_shopifyql to trigger actions in AdminAgent. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
ShopifyQL is Shopify's query language for analytics and reporting. While primarily a Read operation (querying data), the 'run' verb and execution context on an admin system with full store access elevates this to Execute. Misuse could extract sensitive business data (customer info, revenue patterns, product secrets) or potentially modify state depending on ShopifyQL's actual capabilities in this integration.
From the tool's definition Tool name 'run_shopifyql' indicates execution of ShopifyQL queries against a Shopify store database. The server context (AdminAgent with Shopify Admin access) and sibling tools (product management, order cancellation, inventory adjustment) confirm this tool…
Attacks that exploit this kind of access
run_shopifyql. It is categorised as a Execute tool in the AdminAgent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AdminAgent MCP server in PolicyLayer and add a rule for run_shopifyql: 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.
run_shopifyql is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_shopifyql 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 run_shopifyql. 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.
run_shopifyql 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 →