Search emails by query. Returns sanitized email summaries with sensitive content filtered. For broad queries (e.g., all emails from today, weekly summaries, or audit tasks), use a high max_results (100-200) and follow up with nextPageToken to paginate through all results. Some emails may be filte...
AI agents call search_emails to retrieve information from AgentCloak without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs email search and retrieval with built-in safety controls (sanitization, PII redaction, blocklists). It is a pure read operation that queries existing data without side effects. The server's read-only design and filtering mechanisms confirm this is a safe Read classification.
From the tool's definition Tool description explicitly states it 'Search emails by query' and 'Returns sanitized email summaries with sensitive content filtered.' The operation is retrieval-only with PII redaction and security filtering applied.
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 AgentCloak, 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 by query. Returns sanitized email summaries with sensitive content filtered. For broad queries (e.g., all emails from today, weekly summaries, or audit tasks), use a high max_results (100-200) and follow up with nextPageToken to paginate through all results. Some emails may be filtered by security rules and not returned. It is categorised as a Read tool in the AgentCloak MCP Server, which means it retrieves data without modifying state.
Register the AgentCloak 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 AgentCloak. 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 AgentCloak MCP server (ryanfren/agentcloak). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AgentCloak, 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.
8 AgentCloak tools catalogued and risk-classified — across an index of 43,000+ MCP servers.