query_collection_records
Query records from a collection (custom data table) by table name. Supports paging + an optional
This record as markdown: /tools/webcake-storefront/query-collection-records.md
What query_collection_records does on Webcake Storefront
AI agents call query_collection_records 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 query_collection_records is rated Low
This tool retrieves/queries data from a collection without modifying, deleting, or executing arbitrary operations. It supports pagination, a typical pattern for safe read operations. No evidence of side effects, destructive actions, or financial operations. The incomplete description does not suggest capabilities beyond querying, so confidence remains high.
From the tool's definition Tool name 'query_collection_records' and description 'Query records from a collection' indicate data retrieval. The mention of 'Supports paging + an optional' (description appears truncated) reinforces read-only querying of custom data tables.
Attacks that exploit this kind of access
The rule that runs query_collection_records 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 query_collection_records, this is the rule to start with:
query_collection_records 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 query_collection_records call is checked against it from then on.
Questions about query_collection_records
Query records from a collection (custom data table) by table name. Supports paging + an optional. 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 query_collection_records: 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.
query_collection_records 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 query_collection_records 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 query_collection_records. 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.
query_collection_records 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