AI agents call search_emails to retrieve information from IMAP MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations are read-only with no side effects—they query existing data without modifying, deleting, or executing anything. Even though the description is empty, the tool name and server context leave little ambiguity. Severity is low because searching emails poses minimal risk; the worst misuse would be information disclosure of email content the user already has access to.
From the tool's definition Tool name 'search_emails' and server description indicating 'searching, reading' emails as core functionality. No description provided for this specific tool, but context from sibling tools and server purpose clearly indicate this is a retrieval operation.
Documented attack patterns abuse exactly the kind of access search_emails gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and IMAP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_emails:
{
"version": "1",
"default": "deny",
"tools": {
"search_emails": {}
}
}search_emails is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
search_emails. It is categorised as a Read tool in the IMAP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the IMAP MCP Server MCP server in PolicyLayer and add a rule for search_emails: 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 IMAP MCP Server. Nothing to install.
search_emails 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 search_emails 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 search_emails. 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.
search_emails is provided by the IMAP MCP Server MCP server (non-dirty/imap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 IMAP MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 IMAP MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.