AI agents call email_search to retrieve information from UnClick without modifying anything — 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 | — | |
query | string | Yes | |
folder | string | — | |
password | string | — |
Parameters from the server's own tool schema.
This tool retrieves or queries email data from an inbox without creating, modifying, or deleting any content. It is a read-only operation that fits the 'Read' category. The severity is low because inadvertent email searches have minimal blast radius—they may retrieve sensitive information if abused, but do not alter data or trigger external operations.
From the tool's definition Tool name 'email_search' and description 'Search emails in an inbox' indicate a retrieval/query operation with no side effects.
Risk signalsAccepts freeform code/query input (query) · Accepts file system path (folder) · Handles credentials or secrets (password)
Attacks that exploit this kind of access
Search emails in an inbox. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
email_search accepts 5 parameters: email, limit, query, folder, password. Required: query. 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_search: 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_search 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_search 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_search. 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_search is provided by the UnClick MCP server (@unclick/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 →