This record as markdown: /tools/webcake-storefront/get-collection.md
What get_collection does on Webcake Storefront
AI agents call get_collection to retrieve information from Webcake Storefront without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_collection is rated Low
This tool retrieves or queries a collection without side effects. It is a straightforward data access operation consistent with the Read category. The low severity reflects minimal risk if misused by an AI agent, as retrieval operations cannot damage or alter data. The high confidence is based on clear, explicit language indicating a GET/fetch operation.
From the tool's definition Tool name 'get_collection' and description 'Get a specific collection' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs get_collection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Webcake Storefront, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_collection, this is the rule to start with:
get_collection is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every get_collection call is checked against it from then on.
Questions about get_collection
Get a specific collection. It is categorised as a Read tool in the Webcake Storefront MCP Server, which means it retrieves data without modifying state.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for get_collection: 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 Webcake Storefront. Nothing to install.
get_collection 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_collection 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_collection. 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_collection is provided by the Webcake Storefront MCP server (webcake-storefront-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Webcake Storefront, and thousands of servers like it.
This server
Across the catalogue