Search emails using Gmail search syntax.
AI agents call search_emails to retrieve information from MCP Personal Assistant Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries email data without creating, modifying, or deleting messages. It is a read-only operation that returns results based on search parameters, analogous to a database SELECT query. No side effects or data mutations occur. Blast radius is low because the tool cannot modify state or trigger external actions; it only surfaces existing information the user already has access to.
From the tool's definition Tool name is 'search_emails' and description states it 'Search emails using Gmail search syntax' — a query operation with no modification capability.
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 MCP Personal Assistant Agent, 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 using Gmail search syntax. It is categorised as a Read tool in the MCP Personal Assistant Agent MCP Server, which means it retrieves data without modifying state.
Register the MCP Personal Assistant Agent 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 MCP Personal Assistant Agent. 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 MCP Personal Assistant Agent MCP server (zhangzhongnan928/mcp-pa-ai-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Personal Assistant Agent, 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.
19 MCP Personal Assistant Agent tools catalogued and risk-classified — across an index of 43,000+ MCP servers.