This record as markdown: /tools/creativelead-unclick/email-mark-read.md
What email_mark_read does on UnClick
AI agents use email_mark_read 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 |
|---|---|---|---|
uid | string | — | |
email | string | — | |
folder | string | — | |
password | string | — |
Parameters from the server's own tool schema.
Why email_mark_read is rated Medium
This tool modifies email state by changing the read/unread flag, which is a reversible Write operation. It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete content (Destructive), or involve financial transactions (Financial). The blast radius is minimal since marking emails as read is non-destructive and easily undone by marking as unread.
From the tool's definition Tool name 'email_mark_read' and description 'Mark an email as read' indicate modification of email metadata state.
Risk signalsAccepts file system path (folder) · Handles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs email_mark_read 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_mark_read, this is the rule to start with:
email_mark_read 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_mark_read call is checked against it from then on.
Questions about email_mark_read
Mark an email as read. 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_mark_read accepts 4 parameters: uid, email, folder, 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_mark_read: 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_mark_read 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_mark_read 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_mark_read. 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_mark_read 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