This record as markdown: /tools/creativelead-unclick/email-read-inbox.md
What email_read_inbox does on UnClick
AI agents call email_read_inbox to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | — | |
limit | number | — | |
folder | string | — | |
password | string | — |
Parameters from the server's own tool schema.
Why email_read_inbox is rated Low
This tool retrieves/queries email data from an inbox without creating, modifying, or deleting messages. It is a read-only operation. Severity is medium rather than low because email often contains sensitive personal, financial, or confidential information that could be misused if an agent accesses it without proper authorization or context.
From the tool's definition Tool name 'email_read_inbox' and description 'Read emails from an inbox' explicitly indicate data retrieval with no modification or side effects.
Risk signalsAccepts file system path (folder) · Handles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs email_read_inbox 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_read_inbox, this is the rule to start with:
email_read_inbox is read-only, so it stays allowed. 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_read_inbox call is checked against it from then on.
Questions about email_read_inbox
Read emails from an inbox. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
email_read_inbox accepts 4 parameters: email, limit, 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_read_inbox: 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_read_inbox 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 email_read_inbox 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_read_inbox. 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_read_inbox 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