Forward a Gmail message to another recipient.
AI agents use forward_gmail to create or update resources in Google Connections — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Connections environment.
Forwarding a message is a reversible write operation—it creates new email data and changes communication flow but does not delete, irreversibly overwrite, or execute arbitrary code. While it could have social engineering implications if misused by an agent (forwarding sensitive messages to unintended recipients), the operation itself is Write-class.
From the tool's definition The tool name is 'forward_gmail' and the description states it 'Forward[s] a Gmail message to another recipient.' This creates a new message artifact by forwarding content to an additional party, modifying the Gmail account's communication state.
Attacks that exploit this kind of access
Forward a Gmail message to another recipient. It is categorised as a Write tool in the Google Connections MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Connections MCP server in PolicyLayer and add a rule for forward_gmail: 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 Connections. Nothing to install.
forward_gmail 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 forward_gmail 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 forward_gmail. 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.
forward_gmail is provided by the Google Connections MCP server (michaelzrork/google-connections-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →