toggle_confirm_mode
Toggle update confirmation mode. Controls whether update tools ask for user confirmation before saving. -
This record as markdown: /tools/webcake-storefront/toggle-confirm-mode.md
What toggle_confirm_mode does on Webcake Storefront
AI agents use toggle_confirm_mode to create or update resources in Webcake Storefront, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Webcake Storefront environment.
Why toggle_confirm_mode is rated Medium
An AI agent can call toggle_confirm_mode faster than any human can review: one bad instruction and it creates or modifies resources in Webcake Storefront by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs toggle_confirm_mode 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_confirm_mode, this is the rule to start with:
toggle_confirm_mode stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_confirm_mode call is checked against it from then on.
Questions about toggle_confirm_mode
Toggle update confirmation mode. Controls whether update tools ask for user confirmation before saving. -. It is categorised as a Write tool in the Webcake Storefront MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for toggle_confirm_mode: 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_confirm_mode is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the toggle_confirm_mode 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_confirm_mode. 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_confirm_mode 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