shopify_list_collections
AI agents call shopify_list_collections to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' prefix in the tool name strongly indicates a data retrieval operation with no side effects. While the description is empty, the naming convention and context from sibling tools provide high confidence this queries Shopify collections data. Severity is low since listing collections is a non-destructive read operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'shopify_list_collections' indicates a list operation. The naming pattern mirrors sibling 'airtable_list_records', 'airtable_list_bases', and 'amplitude_get_event_counts', all Read operations that retrieve data without modification.
Attacks that exploit this kind of access
shopify_list_collections. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for shopify_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 Integrations MCP. Nothing to install.
shopify_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 shopify_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 shopify_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.
shopify_list_collections is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). 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 →