unified_search
Search across multiple Microsoft 365 content types (email, calendar events, files) in one query.
This record as markdown: /tools/0xka13b-microsoft-mcps/unified-search.md
What unified_search does on Microsoft MCP
AI agents call unified_search 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 total results. Defaults to 50. |
query | string | Yes | Search query string |
entity_types | array | — | Entity types to search. Defaults to [message, event, driveItem]. |
Parameters from the server's own tool schema.
Why unified_search is rated Low
unified_search retrieves and queries data across email, calendar, and files without creating, modifying, or deleting content. This is a Read operation. Severity is medium (not low) because the search spans sensitive content types (emails, calendar events, files) that may contain confidential information; an AI agent with unbounded search could exfiltrate large volumes of sensitive data.
From the tool's definition Tool performs 'Search across multiple Microsoft 365 content types (email, calendar events, files)' — a retrieval operation with no modification or deletion capability.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs unified_search 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 unified_search, this is the rule to start with:
unified_search 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 unified_search call is checked against it from then on.
Questions about unified_search
Search across multiple Microsoft 365 content types (email, calendar events, files) in one query. It is categorised as a Read tool in the Microsoft MCP MCP Server, which means it retrieves data without modifying state.
unified_search accepts 3 parameters: limit, query, entity_types. 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 unified_search: 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.
unified_search 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 unified_search 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 unified_search. 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.
unified_search 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