rename-script

Renames a script by name and folder path

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-script.md

WHAT IT DOES

What rename-script does on Mcp Dev

AI agents use rename-script 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-script is rated Medium

Renaming is a write operation that alters data (the script's name/identifier) but is not destructive because it does not delete content, does not execute code, and can be undone by renaming again. In a CMS context, renaming scripts could disrupt references or automation that depend on the old name, warranting 'medium' severity; however, the core operation is metadata modification (Write category).

From the tool's definition Tool description explicitly states 'Renames a script', which modifies metadata of an existing script resource. The action is reversible—the script can be renamed again to restore the original name.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

rename-script Rate-limited

rename-script 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-script": {
      "limits": [
        {
          "counter": "rename-script_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-script call is checked against it from then on.

FAQ

Questions about rename-script

What does the rename-script tool do? +

Renames a script by name and folder path. 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-script? +

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

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

Can I rate-limit rename-script? +

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

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

rename-script 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 →