rename_files · Local Files MCP Server MCP: Risk & Policy

WHAT IT DOES

What rename_files does on Local Files MCP Server

AI agents use rename_files to create or update resources in Local Files MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local Files MCP Server environment.

WHY IT NEEDS A POLICY

Why rename_files needs a policy

Renaming files is a write operation because it modifies file metadata (names) but does not delete data or execute arbitrary code. While the batch nature and regex support increase blast radius (could rename many files at once if pattern is incorrect), the operation is reversible and does not irreversibly destroy data, so it does not qualify as Destructive.

From the tool's definition Tool performs batch rename operations on files using regex pattern matching. Renaming is a modification operation that creates new file names and overwrites existing metadata, which is reversible—the original files can be renamed back.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_files Rate-limited

rename_files 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_files": {
      "limits": [
        {
          "counter": "rename_files_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Local Files MCP Server, so you can run agents against it safely.

FAQ

Questions about rename_files

What does the rename_files tool do? +

Batch rename files in a directory using regex pattern matching. Supports preview mode. It is categorised as a Write tool in the Local Files MCP Server 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_files? +

Register the Local Files MCP Server MCP server in PolicyLayer and add a rule for rename_files: 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 Local Files MCP Server. Nothing to install.

What risk level is rename_files? +

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

Can I rate-limit rename_files? +

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

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

rename_files is provided by the Local Files MCP Server MCP server (tobiasarg/localfilesorganizer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.