renameFile · Google Docs, Drive & Sheets MCP Server MCP

WHAT IT DOES

What renameFile does on Google Docs, Drive & Sheets MCP Server

AI agents use renameFile to create or update resources in Google Docs, Drive & Sheets MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Docs, Drive & Sheets MCP Server environment.

WHY IT NEEDS A POLICY

Why renameFile needs a policy

Renaming is a metadata modification that creates or modifies file properties. It does not delete data (so not Destructive), does not execute code (not Execute), and does not move money (not Financial). The severity is medium because renaming files can cause confusion or break dependent workflows if done incorrectly by an AI agent, but the operation is fully reversible by renaming again.

From the tool's definition Tool name 'renameFile' and description 'Renames a file or folder in Google Drive' indicate modification of file metadata. This is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

renameFile Rate-limited

renameFile 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": {
    "renameFile": {
      "limits": [
        {
          "counter": "renamefile_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 Google Docs, Drive & Sheets MCP Server, so you can run agents against it safely.

FAQ

Questions about renameFile

What does the renameFile tool do? +

Renames a file or folder in Google Drive. Returns the updated file info. It is categorised as a Write tool in the Google Docs, Drive & Sheets 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 renameFile? +

Register the Google Docs, Drive & Sheets MCP Server MCP server in PolicyLayer and add a rule for renameFile: 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 Google Docs, Drive & Sheets MCP Server. Nothing to install.

What risk level is renameFile? +

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

Can I rate-limit renameFile? +

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

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

renameFile is provided by the Google Docs, Drive & Sheets MCP Server MCP server (rulords/google-docs-mcp-personal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.