This record as markdown: /tools/creativelead-unclick/email-send.md
What email_send does on UnClick
AI agents use email_send to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
cc | string | — | |
to | string | — | |
bcc | string | — | |
body | string | — | |
email | string | — | |
subject | string | — | |
password | string | — |
Parameters from the server's own tool schema.
Why email_send is rated Medium
Sending email is a write operation that modifies state in an external system (Gmail/IMAP). It's not read-only (does not merely retrieve data), not destructive (email can typically be deleted or the action partially mitigated), and not financial.
From the tool's definition Tool name and description: 'email_send' sends an email via Gmail/IMAP. Sending email creates new data (a message) in a remote system and is reversible (recipient can delete, sender can attempt to retract).
Risk signalsAccepts raw HTML/template content (body) · Handles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs email_send safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For email_send, this is the rule to start with:
email_send 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 UnClick, apply this rule, and every email_send call is checked against it from then on.
Questions about email_send
Send an email via Gmail/IMAP. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
email_send accepts 7 parameters: cc, to, bcc, body, email, subject, password. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for email_send: 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 UnClick. Nothing to install.
email_send 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 email_send 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 email_send. 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.
email_send is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue