gmail_users_messages_send

Send a new email to recipients

SERVERGoogle Workspace Gmail (gws CLI) SOURCE@gws mcp -s gmail
High RISK CLASS
Category Execute
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-messages-send.md

What gmail_users_messages_send does on Google Workspace Gmail (gws CLI)

AI agents invoke gmail_users_messages_send to trigger actions in Google Workspace Gmail (gws CLI). What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why gmail_users_messages_send is rated High

Sending an email is an external operation that delivers a message to real recipients and cannot be recalled. It triggers an irreversible external communication action, which fits Execute (external operation). While not Destructive (no data deletion) or Financial, the blast radius is high because a misused agent could send arbitrary emails to any recipients, causing reputational, legal, or social harm.

From the tool's definition "Send a new email to recipients"

Risk signalsSends email from user's account

Questions about gmail_users_messages_send

What does the gmail_users_messages_send tool do? +

Send a new email to recipients. It is categorised as a Execute tool in the Google Workspace Gmail (gws CLI) MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on gmail_users_messages_send? +

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

gmail_users_messages_send is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit gmail_users_messages_send? +

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

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

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