run_bulk_query
AI agents invoke run_bulk_query 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.
Despite the empty description, the naming pattern 'run_bulk_query' in the context of a Shopify Admin MCP server suggests code/query execution. Bulk operations on an e-commerce platform can modify multiple records simultaneously. This is Execute rather than Write because 'bulk_query' implies dynamic, argument-dependent behavior whose effects depend on the query content.
From the tool's definition Tool name 'run_bulk_query' combined with sibling tools showing full store management capabilities (cancel_order, adjust_inventory, capture_payment).
Attacks that exploit this kind of access
run_bulk_query. 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_bulk_query: 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_bulk_query 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_bulk_query 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_bulk_query. 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_bulk_query 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 →