create_permission · Google MCP: Risk & Policy

WHAT IT DOES

What create_permission does on Google

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

WHY IT NEEDS A POLICY

Why create_permission needs a policy

create_permission modifies sharing settings on Google Drive files, allowing an AI agent to grant access to files to arbitrary users or groups. While the change is reversible (permissions can be removed), the high severity reflects the risk of unintended sharing of sensitive documents to external parties or broader audiences.

From the tool's definition Tool description states: 'Share a Google Drive file with a user, group, domain, or anyone.' This modifies file permissions, which is a reversible change to metadata/access control.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_permission Rate-limited

create_permission 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": {
    "create_permission": {
      "limits": [
        {
          "counter": "create_permission_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, so you can run agents against it safely.

FAQ

Questions about create_permission

What does the create_permission tool do? +

Share a Google Drive file with a user, group, domain, or anyone. It is categorised as a Write tool in the Google MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_permission? +

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

What risk level is create_permission? +

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

Can I rate-limit create_permission? +

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

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

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