rename-stylesheet

Renames a stylesheet

SERVERMcp Dev SOURCE@umbraco-cms/mcp-dev

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-dev/rename-stylesheet.md

WHAT IT DOES

What rename-stylesheet does on Mcp Dev

AI agents use rename-stylesheet to create or update resources in Mcp Dev, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Dev environment.

RISK

Why rename-stylesheet is rated Medium

Renaming a stylesheet is a reversible modification operation that changes resource metadata but does not create, delete, or execute external operations. This fits the Write category. Severity is medium because renaming stylesheets in a CMS could affect frontend rendering if dependencies exist, but the change is easily reversible through renaming back to the original name.

From the tool's definition The tool 'rename-stylesheet' performs a rename operation on a stylesheet, which modifies metadata/properties of an existing resource without deleting it. The description explicitly states it 'Renames a stylesheet'.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

rename-stylesheet Rate-limited

rename-stylesheet 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename-stylesheet": {
      "limits": [
        {
          "counter": "rename-stylesheet_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every rename-stylesheet call is checked against it from then on.

FAQ

Questions about rename-stylesheet

What does the rename-stylesheet tool do? +

Renames a stylesheet. It is categorised as a Write tool in the Mcp Dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename-stylesheet? +

Register the Mcp Dev MCP server in PolicyLayer and add a rule for rename-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.

What risk level is rename-stylesheet? +

rename-stylesheet is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rename-stylesheet? +

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

How do I block rename-stylesheet completely? +

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

What MCP server provides rename-stylesheet? +

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

KEEP EXPLORING

More on Mcp Dev, and thousands of servers like it.

This server

All 419 Mcp Dev tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →