This record as markdown: /tools/webcake-storefront/remove-font-group.md
What remove_font_group does on Webcake Storefront
AI agents call remove_font_group to permanently remove resources in Webcake Storefront, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_font_group is rated Critical
The 'remove' action applied to a font group constitutes an irreversible deletion operation. While the blast radius is scoped to a single design component (font group) rather than critical data like orders or customer records, deletion of storefront styling assets can disrupt site appearance and is not easily recoverable.
From the tool's definition Tool name contains 'remove' and description states 'Remove a font group by id' — this indicates irreversible deletion of a design asset.
Attacks that exploit this kind of access
The rule that runs remove_font_group 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 remove_font_group, this is the rule to start with:
remove_font_group is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every remove_font_group call is checked against it from then on.
Questions about remove_font_group
Remove a font group by id. It is categorised as a Destructive tool in the Webcake Storefront MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for remove_font_group: 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.
remove_font_group is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_font_group 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 remove_font_group. 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.
remove_font_group 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