rename_file

Rename a file.

SERVERMcp Google Docs SOURCEdev-ithitchhiker/mcp-google-docs

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/dev-ithitchhiker-mcp-google-docs/rename-file.md

WHAT IT DOES

What rename_file does on Mcp Google Docs

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

RISK

Why rename_file is rated Medium

Renaming a file is a write operation that modifies file metadata. It is reversible (can be renamed back) and has no destructive or irreversible consequences. Severity is medium because an agent could rename critical files to misleading names, causing operational confusion, but the change itself is not permanent or data-destructive.

From the tool's definition The tool description states it 'Rename a file.' Renaming is a reversible modification operation that changes metadata without destroying 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 Mcp Google Docs, 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 Mcp Google Docs, 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 a file. It is categorised as a Write tool in the Mcp Google Docs 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 Mcp Google Docs 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 Mcp Google Docs. 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 Mcp Google Docs MCP server (dev-ithitchhiker/mcp-google-docs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Google Docs, and thousands of servers like it.

This server

All 55 Mcp Google Docs tools →

Across the catalogue

write_file on 0sec → The MCP Attack Database →

Guides

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