remove_font

Remove a font by id.

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/webcake-storefront/remove-font.md

WHAT IT DOES

What remove_font does on Webcake Storefront

AI agents call remove_font 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.

RISK

Why remove_font is rated Critical

This tool deletes a font asset by identifier. Deletion is irreversible—the font cannot be recovered after removal. In a storefront context, removing a font could break page rendering if the font is in active use across multiple pages, causing visual defects that would require restoration from backups or re-adding the font manually.

From the tool's definition Tool name 'remove_font' combined with description 'Remove a font by id' indicates irreversible deletion of a resource.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_font 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, this is the rule to start with:

remove_font Hidden

remove_font is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_font"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every remove_font call is checked against it from then on.

FAQ

Questions about remove_font

What does the remove_font tool do? +

Remove a font 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.

How do I enforce a policy on remove_font? +

Register the Webcake Storefront MCP server in PolicyLayer and add a rule for remove_font: 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.

What risk level is remove_font? +

remove_font is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_font? +

Yes. Add a rate_limit block to the remove_font 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.

How do I block remove_font completely? +

Set action: deny in the PolicyLayer policy for remove_font. 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.

What MCP server provides remove_font? +

remove_font 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.

KEEP EXPLORING

More on Webcake Storefront, and thousands of servers like it.

This server

All 287 Webcake Storefront tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →