list_cached_results

List the large results currently held in the session cache (id, label, size, age).

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/webcake-storefront/list-cached-results.md

WHAT IT DOES

What list_cached_results does on Webcake Storefront

AI agents call list_cached_results 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.

RISK

Why list_cached_results is rated Low

This tool retrieves metadata about cached results (id, label, size, age) without modifying, deleting, or executing any operations. It is a read-only query of session state, making it a Read category tool with low severity since cache information disclosure poses minimal risk to the storefront.

From the tool's definition Tool name is 'list_cached_results' and description states it 'List[s] the large results currently held in the session cache'. The verb 'list' and the action of querying cached data retrieves information with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_cached_results 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 list_cached_results, this is the rule to start with:

list_cached_results Allowed

list_cached_results is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_cached_results": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every list_cached_results call is checked against it from then on.

FAQ

Questions about list_cached_results

What does the list_cached_results tool do? +

List the large results currently held in the session cache (id, label, size, age). It is categorised as a Read tool in the Webcake Storefront MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_cached_results? +

Register the Webcake Storefront MCP server in PolicyLayer and add a rule for list_cached_results: 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.

What risk level is list_cached_results? +

list_cached_results is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_cached_results? +

Yes. Add a rate_limit block to the list_cached_results 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.

How do I block list_cached_results completely? +

Set action: deny in the PolicyLayer policy for list_cached_results. 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.

What MCP server provides list_cached_results? +

list_cached_results 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.

KEEP EXPLORING

More on Webcake Storefront, and thousands of servers like it.

This server

All 287 Webcake Storefront tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server →get_event_results on CTFtime MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →