list_cms_files

List all CMS files (HTTP functions, cron jobs, ...) for the site

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-cms-files.md

WHAT IT DOES

What list_cms_files does on Webcake Storefront

AI agents call list_cms_files 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_cms_files is rated Low

This tool only retrieves and enumerates CMS files (HTTP functions, cron jobs, etc.) without modifying, executing, or deleting them. It is a read-only query operation with minimal blast radius even if misused by an AI agent, as it simply exposes metadata about existing files.

From the tool's definition Tool name explicitly starts with 'list' and description states it 'List[s] all CMS files' — pure retrieval with no modification, execution, or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_cms_files Allowed

list_cms_files 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_cms_files": {}
  }
}

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_cms_files call is checked against it from then on.

FAQ

Questions about list_cms_files

What does the list_cms_files tool do? +

List all CMS files (HTTP functions, cron jobs, ...) for the site. 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_cms_files? +

Register the Webcake Storefront MCP server in PolicyLayer and add a rule for list_cms_files: 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_cms_files? +

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

Can I rate-limit list_cms_files? +

Yes. Add a rate_limit block to the list_cms_files 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_cms_files completely? +

Set action: deny in the PolicyLayer policy for list_cms_files. 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_cms_files? +

list_cms_files 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 → The MCP Attack Database →

Guides

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