addPermission

SERVERGoogle Drive SOURCE@ark7/google-drive-mcp

Medium RISK CLASS

Category Write

Parameters 91 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ark7-google-drive-mcp/addpermission.md

WHAT IT DOES

What addPermission does on Google Drive

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

Parameter	Type	Required	Description
`role`	string	—	Permission role
`type`	string	—	Principal type
`domain`	string	—	Target domain, e.g. 'example.com'. Required when type is 'domain'; ignored otherwise.
`fileId`	string	Yes	Google Drive file ID
`account`	string	—	Alias of the Google account to target. Optional — defaults to the session/global default account, or the sole authenticated account. Run manage_accounts list to
`emailAddress`	string	—	Target user/group email. Required when type is 'user' or 'group'; ignored for 'domain'/'anyone'.
`emailMessage`	string	—	Custom message to include in the notification email. Ignored unless sendNotificationEmail is true.
`allowFileDiscovery`	boolean	—	Only for type 'domain'/'anyone': false (default) = accessible with the link only; true = discoverable in search. Ignored for 'user'/'group'.
`sendNotificationEmail`	boolean	—	Send notification email

Parameters from the server's own tool schema.

RISK

Why addPermission is rated Medium

An AI agent can call addPermission faster than any human can review: one bad instruction and it creates or modifies resources in Google Drive by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs addPermission safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For addPermission, this is the rule to start with:

addPermission Rate-limited

addPermission 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": {
    "addPermission": {
      "limits": [
        {
          "counter": "addpermission_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Google Drive, apply this rule, and every addPermission call is checked against it from then on.

FAQ

Questions about addPermission

What does the addPermission tool do? +

Add a sharing permission to a file. If the principal already holds a permission on the file, Drive updates that permission instead of creating a second one, and the requested role is applied even when it is a downgrade (asking for 'reader' for an existing 'writer' leaves them as 'reader'). Provide emailAddress for type 'user'/'group', domain for type 'domain', and neither for 'anyone'. It is categorised as a Write tool in the Google Drive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does addPermission accept? +

addPermission accepts 9 parameters: role, type, domain, fileId, account, emailAddress, emailMessage, allowFileDiscovery, sendNotificationEmail. Required: fileId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on addPermission? +

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

What risk level is addPermission? +

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

Can I rate-limit addPermission? +

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

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

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

KEEP EXPLORING

More on Google Drive, and thousands of servers like it.

This server

All 131 Google Drive tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →