drive_permission_add_anyone · Google Drive MCP Server MCP

WHAT IT DOES

What drive_permission_add_anyone does on Google Drive MCP Server

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

WHY IT NEEDS A POLICY

Why drive_permission_add_anyone needs a policy

This tool modifies file permissions to make resources publicly accessible, which is a write operation (reversible configuration change) rather than read-only or destructive.

From the tool's definition 'Allow anyone with the link to access a file or folder' describes modification of file permissions, which is a reversible change to access controls. The tool name contains 'permission_add' confirming it modifies sharing permissions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drive_permission_add_anyone Rate-limited

drive_permission_add_anyone 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_permission_add_anyone": {
      "limits": [
        {
          "counter": "drive_permission_add_anyone_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 Drive MCP Server, so you can run agents against it safely.

FAQ

Questions about drive_permission_add_anyone

What does the drive_permission_add_anyone tool do? +

Allow anyone with the link to access a file or folder. It is categorised as a Write tool in the Google Drive 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_permission_add_anyone? +

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

What risk level is drive_permission_add_anyone? +

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

Can I rate-limit drive_permission_add_anyone? +

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

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

drive_permission_add_anyone is provided by the Google Drive MCP Server MCP server (rishipradeep-think41/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.