drive_file_restore · TrekMail MCP Server MCP: Risk & Policy

WHAT IT DOES

What drive_file_restore does on TrekMail MCP Server

AI agents use drive_file_restore 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_restore needs a policy

This tool performs a reversible state modification—restoring a soft-deleted file to an accessible location. It does not permanently destroy data (which would be Destructive) nor execute arbitrary code (Execute). The restoration is reversible: the file could be trashed again.

From the tool's definition Tool description states 'Un-trash a soft-deleted file', indicating it restores and modifies the state of a previously deleted file by moving it from trash to an accessible location (root or parent folder).

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drive_file_restore Rate-limited

drive_file_restore 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_restore": {
      "limits": [
        {
          "counter": "drive_file_restore_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_restore

What does the drive_file_restore tool do? +

Un-trash a soft-deleted file. If parent folder is also trashed, file pops up at root. 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_restore? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for drive_file_restore: 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_restore? +

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

Can I rate-limit drive_file_restore? +

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

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

drive_file_restore 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.