send-email
Send new email or reply. Returns: sent message id and threadId. Use when: composing new email or replying to thread. For replies: provide replyToMessageId.
This record as markdown: /tools/199-biotechnologies-mcp-google/send-email.md
What send-email does on MCP Google Workspace
AI agents use send-email to create or update resources in MCP Google Workspace, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Google Workspace environment.
Why send-email is rated Medium
The tool creates and sends emails, which modifies the user's email account and communication state. While not destructive (emails can be recalled or deleted), and not financial, it is a Write operation that could have significant consequences if misused by an AI agent (e.g., sending emails to unintended recipients, composing misleading messages, or spamming).
From the tool's definition Tool name is 'send-email' and description states 'Send new email or reply' — this creates new messages and modifies email threads by adding replies.
Attacks that exploit this kind of access
The rule that runs send-email safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Google Workspace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send-email, this is the rule to start with:
send-email 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 MCP Google Workspace, apply this rule, and every send-email call is checked against it from then on.
Questions about send-email
Send new email or reply. Returns: sent message id and threadId. Use when: composing new email or replying to thread. For replies: provide replyToMessageId. It is categorised as a Write tool in the MCP Google Workspace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Google Workspace MCP server in PolicyLayer and add a rule for send-email: 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 MCP Google Workspace. Nothing to install.
send-email 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 send-email 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 send-email. 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.
send-email is provided by the MCP Google Workspace MCP server (199-mcp/mcp-google). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Google Workspace, and thousands of servers like it.
This server
Across the catalogue