new_element
Build a single structurally-valid element node from the real builder factory. Returns the node — edit its specials/style, then place it in a section
This record as markdown: /tools/webcake-storefront/new-element.md
What new_element does on Webcake Storefront
AI agents use new_element 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 new_element is rated Medium
The tool creates a new element node in the page builder. This is a write/create operation that constructs a new data structure. It is reversible (the node can be discarded or deleted), and it has limited blast radius as it only builds a node for later placement rather than directly modifying live content.
From the tool's definition Build a single structurally-valid element node from the real builder factory. Returns the node — edit its specials/style, then place it in a section
Attacks that exploit this kind of access
The rule that runs new_element 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_element, this is the rule to start with:
new_element 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 new_element call is checked against it from then on.
Questions about new_element
Build a single structurally-valid element node from the real builder factory. Returns the node — edit its specials/style, then place it in a section. 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 new_element: 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_element 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 new_element 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_element. 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_element 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