rename_file

Rename or move a file

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

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/cowork-os/rename-file.md

WHAT IT DOES

What rename_file does on CoWork OS

AI agents use rename_file to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.

RISK

Why rename_file is rated Medium

Renaming or moving a file is a reversible operation that modifies data organization without permanent destruction. It qualifies as Write rather than Destructive because the data remains intact and recoverable. Severity is medium because misuse could reorganize critical files or move them to inaccessible locations, but the effects are not permanent or catastrophic like deletion.

From the tool's definition Tool name 'rename_file' and description 'Rename or move a file' indicate it modifies file metadata and location but does not delete or irreversibly destroy data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rename_file safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rename_file, this is the rule to start with:

rename_file Rate-limited

rename_file 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_file": {
      "limits": [
        {
          "counter": "rename_file_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 CoWork OS, apply this rule, and every rename_file call is checked against it from then on.

FAQ

Questions about rename_file

What does the rename_file tool do? +

Rename or move a file. It is categorised as a Write tool in the CoWork OS 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_file? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for rename_file: 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 CoWork OS. Nothing to install.

What risk level is rename_file? +

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

Can I rate-limit rename_file? +

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

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

rename_file is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

The MCP Attack Database →

Guides

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