gmail_send_message_with_attachment
A write tool on the Gmail MCP server.
This record as markdown: /tools/ampcome-mcps-gmail-mcp/gmail-send-message-with-attachment.md
What gmail_send_message_with_attachment does on Gmail MCP Server
AI agents use gmail_send_message_with_attachment to create or update resources in Gmail MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gmail MCP Server environment.
Why gmail_send_message_with_attachment is rated Medium
Sending emails is a reversible write operation that creates new data (messages) in a user's account and potentially affects external recipients. While not destructive or financial in nature, it carries high severity because an AI agent could send spam, phishing messages, or inappropriately disclose sensitive information to unintended recipients.
From the tool's definition Tool name 'gmail_send_message_with_attachment' indicates creation of new email messages with attachments. Server description confirms 'sending' emails is a core capability.
Attacks that exploit this kind of access
The rule that runs gmail_send_message_with_attachment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gmail MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gmail_send_message_with_attachment, this is the rule to start with:
gmail_send_message_with_attachment 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 Gmail MCP Server, apply this rule, and every gmail_send_message_with_attachment call is checked against it from then on.
Questions about gmail_send_message_with_attachment
gmail_send_message_with_attachment is a write tool on the Gmail MCP Server MCP server. It is categorised as a Write tool in the Gmail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gmail MCP Server MCP server in PolicyLayer and add a rule for gmail_send_message_with_attachment: 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 Gmail MCP Server. Nothing to install.
gmail_send_message_with_attachment 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 gmail_send_message_with_attachment 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 gmail_send_message_with_attachment. 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.
gmail_send_message_with_attachment is provided by the Gmail MCP Server MCP server (ampcome-mcps/gmail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gmail MCP Server, and thousands of servers like it.
This server
Across the catalogue