gmail_search
Search Gmail messages in the connected mailbox.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/gmail-search.md
What gmail_search does on UnClick
AI agents call gmail_search 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 |
|---|---|---|---|
limit | number | — | Messages to return (max 100, default 10) |
query | string | — | Gmail search query, such as from:alice newer_than:7d |
page_token | string | — | Gmail page token from a previous response |
access_token | string | — | Gmail access token |
Parameters from the server's own tool schema.
Why gmail_search is rated Low
This tool queries and retrieves existing email messages from a Gmail account. It has no side effects—it does not create, modify, delete, or execute actions. However, the severity is medium rather than low because unauthorized access to email messages could expose sensitive personal information, credentials, or private communications, making it a moderate risk if misused by an AI agent with access to someone's…
From the tool's definition Tool name 'gmail_search' and description 'Search Gmail messages in the connected mailbox' indicates retrieval of email data without modification.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs gmail_search 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 gmail_search, this is the rule to start with:
gmail_search 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 gmail_search call is checked against it from then on.
Questions about gmail_search
Search Gmail messages in the connected mailbox. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
gmail_search accepts 4 parameters: limit, query, page_token, access_token. 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 gmail_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.
gmail_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 gmail_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 gmail_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.
gmail_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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue