Forward an email to another recipient
AI agents use forward_email to create or update resources in Enhanced MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Enhanced MCP Server environment.
Forwarding an email sends existing email content to a new recipient. This is a Write operation as it creates a new outbound email message. Severity is high because misuse could cause data leakage — confidential email content could be forwarded to unauthorized parties — but the action is not strictly irreversible in the same way deletion is.
From the tool's definition Forward an email to another recipient
Attacks that exploit this kind of access
Forward an email to another recipient. It is categorised as a Write tool in the Enhanced MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Enhanced MCP Server MCP server in PolicyLayer and add a rule for forward_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 Enhanced MCP Server. Nothing to install.
forward_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 forward_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 forward_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.
forward_email is provided by the Enhanced MCP Server MCP server (pbulbule13/mcpwithgoogle). 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 →