gmail_users_settings_delegates_create
Add a mailbox delegate with access
This record as markdown: /tools/google-workspace-gmail/gmail-users-settings-delegates-create.md
What gmail_users_settings_delegates_create does on Google Workspace Gmail (gws CLI)
AI agents use gmail_users_settings_delegates_create to create or update resources in Google Workspace Gmail (gws CLI), usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Workspace Gmail (gws CLI) environment.
Why gmail_users_settings_delegates_create is rated Medium
This tool modifies Gmail account security settings by adding a delegate (another user) who gains access to read, send, and manage emails on behalf of the account owner. While it creates a reversible configuration change (not a destructive delete operation) and doesn't directly move money or execute arbitrary code, it has significant security implications and constitutes a Write operation that alters account…
From the tool's definition Tool name includes 'create' and description states 'Add a mailbox delegate with access' — this creates a new delegation relationship that grants another user access to the mailbox.
Risk signalsGrants mailbox access to another user
Attacks that exploit this kind of access
The rule that runs gmail_users_settings_delegates_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Workspace Gmail (gws CLI), and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gmail_users_settings_delegates_create, this is the rule to start with:
gmail_users_settings_delegates_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Workspace Gmail (gws CLI), apply this rule, and every gmail_users_settings_delegates_create call is checked against it from then on.
Questions about gmail_users_settings_delegates_create
Add a mailbox delegate with access. It is categorised as a Write tool in the Google Workspace Gmail (gws CLI) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Workspace Gmail (gws CLI) MCP server in PolicyLayer and add a rule for gmail_users_settings_delegates_create: 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 Gmail (gws CLI). Nothing to install.
gmail_users_settings_delegates_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gmail_users_settings_delegates_create 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.
Set action: deny in the PolicyLayer policy for gmail_users_settings_delegates_create. 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.
gmail_users_settings_delegates_create is provided by the Google Workspace Gmail (gws CLI) MCP server (@gws mcp -s gmail). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Workspace Gmail (gws CLI), and thousands of servers like it.
This server
Across the catalogue