search_emails
Search emails by keyword across all folders or within a specific folder (KQL syntax supported).
This record as markdown: /tools/0xka13b-microsoft-mcps/search-emails.md
What search_emails does on Microsoft MCP
AI agents call search_emails to retrieve information from Microsoft MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max results. Defaults to 50. |
query | string | Yes | Search query string |
folder | string | — | Limit search to this folder (inbox, sent, etc.) |
Parameters from the server's own tool schema.
Why search_emails is rated Low
This tool queries and retrieves email messages based on search criteria (KQL syntax). It has no side effects—no data is created, modified, deleted, or executed. The blast radius is minimal: an AI agent could exfiltrate email content, but cannot alter or destroy data. Categorized as Read per the definition: 'retrieves or queries data; no side effects.'
From the tool's definition Tool name 'search_emails' and description stating it 'Search emails by keyword across all folders or within a specific folder' indicates retrieval of email data. No modification, deletion, or execution capabilities are mentioned.
Risk signalsAccepts freeform code/query input (query) · Accepts file system path (folder)
Attacks that exploit this kind of access
The rule that runs search_emails safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Microsoft MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_emails, this is the rule to start with:
search_emails is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Microsoft MCP, apply this rule, and every search_emails call is checked against it from then on.
Questions about search_emails
Search emails by keyword across all folders or within a specific folder (KQL syntax supported). It is categorised as a Read tool in the Microsoft MCP MCP Server, which means it retrieves data without modifying state.
search_emails accepts 3 parameters: limit, query, folder. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Microsoft 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 Microsoft MCP. 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 Microsoft MCP server (0xka13b/microsoft-mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Microsoft, and thousands of servers like it.
This server
Across the catalogue