Low Risk

mail_search

Search emails in a mailbox. Returns message list with uid, from, to, subject, date, flags.

How to control mail_search ↓

What mail_search does on Shellgate

AI agents call mail_search to retrieve information from Shellgate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why mail_search needs a policy

mail_search performs a read-only query operation on email data. It retrieves and returns email metadata without creating, modifying, deleting, or executing any actions. The tool has no side effects and poses minimal security risk when misused by an AI agent, as it cannot alter mailbox state or trigger external operations.

From the tool's definition Tool description explicitly states it 'Search emails in a mailbox' and 'Returns message list with uid, from, to, subject, date, flags' — a retrieval operation with no modification or deletion capability.

Documented attack patterns abuse exactly the kind of access mail_search gives an agent:

How to control mail_search

PolicyLayer is an MCP gateway — it sits between your AI agents and Shellgate, and nothing reaches the server without passing your rules. This is the rule we recommend for mail_search:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mail_search": {}
  }
}

mail_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Shellgate — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about mail_search

What does the mail_search tool do? +

Search emails in a mailbox. Returns message list with uid, from, to, subject, date, flags. It is categorised as a Read tool in the Shellgate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mail_search? +

Register the Shellgate MCP server in PolicyLayer and add a rule for mail_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 Shellgate. Nothing to install.

What risk level is mail_search? +

mail_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mail_search? +

Yes. Add a rate_limit block to the mail_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.

How do I block mail_search completely? +

Set action: deny in the PolicyLayer policy for mail_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.

What MCP server provides mail_search? +

mail_search is provided by the Shellgate MCP server (matthiastjong/shellgate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Shellgate tool call.

Start from Shellgate, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

31 Shellgate tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.