restore_file · Google Docs MCP Server MCP: Risk & Policy

WHAT IT DOES

What restore_file does on Google Docs MCP Server

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

WHY IT NEEDS A POLICY

Why restore_file needs a policy

This tool performs a reversible modification operation—restoring a trashed file to its accessible state. It does not permanently delete (which would be Destructive) nor does it read/query data without side effects (Read). The ability to restore files that were previously deleted could be misused by an agent to recover sensitive data an owner wanted permanently removed, or to undo intentional file deletions.

From the tool's definition Tool restores a file from trash, which modifies the state of files in Google Drive by moving them from the trash back to active storage. The description explicitly states 'Restore a file from trash.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restore_file Rate-limited

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

FAQ

Questions about restore_file

What does the restore_file tool do? +

Restore a file from trash. It is categorised as a Write tool in the Google Docs 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 restore_file? +

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

What risk level is restore_file? +

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

Can I rate-limit restore_file? +

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

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

restore_file is provided by the Google Docs MCP Server MCP server (nickweedon/google-docs-mcp-docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.