outlook_search_messages
Search email messages using Microsoft Graph $search query syntax. Searches across subject, body, and other fields.
This record as markdown: /tools/sagemcp-sagemcp/outlook-search-messages.md
What outlook_search_messages does on Sage MCP
AI agents call outlook_search_messages to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why outlook_search_messages is rated Low
Email search is fundamentally a read operation that queries and retrieves data without side effects. Severity is medium rather than low because email often contains sensitive personal, financial, or business information (credentials, health details, financial statements), and an AI agent with unconstrained search could aggregate and exfiltrate substantial volumes of sensitive data.
From the tool's definition Tool name 'outlook_search_messages' and description 'Search email messages' indicate retrieval of email data with no modification capability. The scope includes 'subject, body, and other fields' confirming query-only operations.
Attacks that exploit this kind of access
The rule that runs outlook_search_messages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For outlook_search_messages, this is the rule to start with:
outlook_search_messages 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 Sage MCP, apply this rule, and every outlook_search_messages call is checked against it from then on.
Questions about outlook_search_messages
Search email messages using Microsoft Graph $search query syntax. Searches across subject, body, and other fields. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for outlook_search_messages: 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 Sage MCP. Nothing to install.
outlook_search_messages 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 outlook_search_messages 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 outlook_search_messages. 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.
outlook_search_messages is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sage, and thousands of servers like it.
This server
Across the catalogue