drive_file_rename · TrekMail MCP Server MCP: Risk & Policy

WHAT IT DOES

What drive_file_rename does on TrekMail MCP Server

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

WHY IT NEEDS A POLICY

Why drive_file_rename needs a policy

File renaming is a write operation that modifies file metadata reversibly. It does not delete data (not Destructive), does not execute code (not Execute), and does not involve financial transactions (not Financial). The medium severity reflects that renaming files could cause confusion or disrupt workflows if misused, but the operation is reversible.

From the tool's definition Tool description states 'Rename a file', which is a reversible modification operation. The presence of validation for name parameters indicates this modifies file metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drive_file_rename Rate-limited

drive_file_rename 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": {
    "drive_file_rename": {
      "limits": [
        {
          "counter": "drive_file_rename_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 TrekMail MCP Server, so you can run agents against it safely.

FAQ

Questions about drive_file_rename

What does the drive_file_rename tool do? +

Rename a file. Validation: name passes the DriveItemName ruleset. It is categorised as a Write tool in the TrekMail 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 drive_file_rename? +

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

What risk level is drive_file_rename? +

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

Can I rate-limit drive_file_rename? +

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

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

drive_file_rename is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.