Send an email
AI agents use send_email to create or update resources in Email MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Email MCP Server environment.
Sending an email is a Write action (creates new data/communication) rather than Read (no retrieval) or Destructive (email transmission is not typically undoable in the same way as deletion, though it has lasting consequences). However, this carries high severity because an AI agent misusing this tool could send unintended emails to wrong recipients, leak sensitive information, or generate reputational damage.
From the tool's definition Tool name 'send_email' with description 'Send an email' performs an irreversible action that creates and transmits a message to recipients. The server context shows this is integrated with Gmail for managing inbox operations.
Attacks that exploit this kind of access
Send an email. It is categorised as a Write tool in the Email MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Email MCP Server 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 Email MCP Server. 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 Email MCP Server MCP server (sgroi-l/email-mcp-server). 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 →