gmail_users_settings_sendAs_update

Update a send-as alias

SERVERGoogle Workspace Gmail (gws CLI) SOURCE@gws mcp -s gmail
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/google-workspace-gmail/gmail-users-settings-sendas-update.md

What gmail_users_settings_sendAs_update does on Google Workspace Gmail (gws CLI)

AI agents use gmail_users_settings_sendAs_update 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_sendAs_update is rated Medium

This tool modifies Gmail account configuration (send-as aliases) in a reversible manner. While it doesn't create permanent destructive changes, allowing an AI to modify email sending identities poses a medium-severity risk: it could enable email spoofing, impersonation, or sending emails that appear to come from different addresses without the user's knowledge.

From the tool's definition Tool name contains 'update' and description states 'Update a send-as alias', indicating modification of Gmail settings that change how emails are sent from an account.

Risk signalsModifies send-as alias settings

Questions about gmail_users_settings_sendAs_update

What does the gmail_users_settings_sendAs_update tool do? +

Update a send-as alias. 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.

How do I enforce a policy on gmail_users_settings_sendAs_update? +

Register the Google Workspace Gmail (gws CLI) MCP server in PolicyLayer and add a rule for gmail_users_settings_sendAs_update: 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.

What risk level is gmail_users_settings_sendAs_update? +

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

Can I rate-limit gmail_users_settings_sendAs_update? +

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

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

gmail_users_settings_sendAs_update 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Google Workspace Gmail (gws CLI)'s. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.