Search for emails using a search query
AI agents call search_emails to retrieve information from Outlook MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search is a classic Read operation—it retrieves and queries data without modifying, deleting, or executing code. Severity is medium (not low) because email search could expose sensitive information if an agent queries for confidential messages; however, it causes no data loss or financial harm. Confidence is high because the name and description are explicit and unambiguous.
From the tool's definition Tool description states 'Search for emails using a search query'. The verb 'search' and the parent server's description emphasizing 'reading, searching' emails indicates this is a read-only operation with no side effects.
Attacks that exploit this kind of access
Search for emails using a search query. It is categorised as a Read tool in the Outlook MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Outlook 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 Outlook 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 Outlook MCP Server MCP server (ryoshin0830/outlook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →