addAccount · Google Workspace MCP Server MCP: Risk & Policy

WHAT IT DOES

What addAccount does on Google Workspace MCP Server

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

WHY IT NEEDS A POLICY

Why addAccount needs a policy

This tool creates/adds a new account configuration to the system by initiating OAuth authorization. It is a Write operation as it establishes a new account association, which is reversible (the account can be removed). Medium severity because adding an unauthorized Google account could grant unwanted access to workspace resources.

From the tool's definition Starts the OAuth flow to add a new Google account... After authorizing, the account will be added automatically.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

addAccount Rate-limited

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

FAQ

Questions about addAccount

What does the addAccount tool do? +

Starts the OAuth flow to add a new Google account. Returns an authorization URL that must be opened in a browser. After authorizing, the account will be added automatically. The account name must be unique and contain only letters, numbers, underscores, and hyphens. Optionally, you can specify a custom credentials file to use a different OAuth app for this account. It is categorised as a Write tool in the Google Workspace 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 addAccount? +

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

What risk level is addAccount? +

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

Can I rate-limit addAccount? +

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

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

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