toggle_debug_render
Toggle debug render mode for a CMS file
This record as markdown: /tools/webcake-storefront/toggle-debug-render.md
What toggle_debug_render does on Webcake Storefront
AI agents invoke toggle_debug_render to trigger actions in Webcake Storefront. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why toggle_debug_render is rated High
Toggling debug render mode changes the execution/rendering behavior of a CMS file. It triggers an external operation (mode change) that affects how the system processes and renders content. It's not a simple data read/write, but a mode switch that alters system behavior, placing it in Execute. Severity is medium as misuse could expose debug information or alter site rendering unexpectedly.
From the tool's definition Toggle debug render mode for a CMS file
Attacks that exploit this kind of access
The rule that runs toggle_debug_render 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 toggle_debug_render, this is the rule to start with:
toggle_debug_render stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 toggle_debug_render call is checked against it from then on.
Questions about toggle_debug_render
Toggle debug render mode for a CMS file. It is categorised as a Execute tool in the Webcake Storefront MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for toggle_debug_render: 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.
toggle_debug_render is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the toggle_debug_render 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 toggle_debug_render. 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.
toggle_debug_render 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.
Across the catalogue