This record as markdown: /tools/mcp-dev/delete-stylesheet.md
What delete-stylesheet does on Mcp Dev
AI agents call delete-stylesheet to permanently remove resources in Mcp Dev, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete-stylesheet is rated Critical
This tool irreversibly removes a stylesheet resource from the Umbraco CMS. Deletion cannot be undone without external backup/recovery mechanisms, making it Destructive rather than Write. The severity is high because stylesheets are typically critical frontend assets; their loss could break site rendering and functionality. High confidence due to explicit use of 'delete' in both name and description.
From the tool's definition Tool name includes 'delete' and description states 'Deletes a stylesheet by its path'
Attacks that exploit this kind of access
The rule that runs delete-stylesheet safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete-stylesheet, this is the rule to start with:
delete-stylesheet 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 Mcp Dev, apply this rule, and every delete-stylesheet call is checked against it from then on.
Questions about delete-stylesheet
Deletes a stylesheet by its path. It is categorised as a Destructive tool in the Mcp Dev MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for delete-stylesheet: 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 Mcp Dev. Nothing to install.
delete-stylesheet 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 delete-stylesheet 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 delete-stylesheet. 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.
delete-stylesheet is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Dev, and thousands of servers like it.
Across the catalogue