new_page_skeleton
Return an empty but valid page source: { sections: [] }. Add sections built with new_section, then save with build_page.
This record as markdown: /tools/webcake-storefront/new-page-skeleton.md
What new_page_skeleton does on Webcake Storefront
AI agents call new_page_skeleton 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 new_page_skeleton is rated Low
This tool only returns a static, empty data structure (a skeleton page object). It does not read from a database, write to any system, or trigger any side effects. It is essentially a template/scaffold generator with no external interactions.
From the tool's definition Return an empty but valid page source: { sections: [] }
Attacks that exploit this kind of access
The rule that runs new_page_skeleton 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 new_page_skeleton, this is the rule to start with:
new_page_skeleton 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 new_page_skeleton call is checked against it from then on.
Questions about new_page_skeleton
Return an empty but valid page source: { sections: [] }. Add sections built with new_section, then save with build_page. 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 new_page_skeleton: 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.
new_page_skeleton 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 new_page_skeleton 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 new_page_skeleton. 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.
new_page_skeleton 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