list_collections
AI agents call list_collections 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 conventionally denotes read-only query operations that retrieve and display data without side effects. No description is provided, but the name and functional context (Shopify Admin collection management) strongly indicate a read operation to enumerate existing collections. This has minimal blast radius if misused by an AI agent—it merely exposes shop structure information.
From the tool's definition Tool name 'list_collections' indicates a listing/retrieval operation with no parameters that would modify data. In the context of a Shopify Admin server managing products and collections, this tool retrieves collection information.
Attacks that exploit this kind of access
list_collections. 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_collections: 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_collections 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_collections 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_collections. 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_collections 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 →