Preview an email without sending it. Returns the formatted message.
AI agents call send_email_preview to retrieve information from Gworkspace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool explicitly states it does NOT send the email — it only previews and returns the formatted message. This is a read/display operation with no side effects.
From the tool's definition Preview an email without sending it. Returns the formatted message.
Attacks that exploit this kind of access
Preview an email without sending it. Returns the formatted message. It is categorised as a Read tool in the Gworkspace MCP Server, which means it retrieves data without modifying state.
Register the Gworkspace MCP server in PolicyLayer and add a rule for send_email_preview: 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 Gworkspace. Nothing to install.
send_email_preview is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the send_email_preview 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_preview. 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_preview is provided by the Gworkspace MCP server (leoonic/gworkspace-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 →