Primary tool for querying Outlook emails with custom OData filters. Build precise server-side filters for dates, read status, importance, subjects, attachments, and conversations. Best for structured queries on message metadata. Returns up to 100 messages per request with pagination support. • Se...
Accepts file system path (folder)
Part of the Outlook MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call OUTLOOK_QUERY_EMAILS to retrieve information from Outlook without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though OUTLOOK_QUERY_EMAILS only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
OUTLOOK_QUERY_EMAILS:
rules:
- action: allowSee the full Outlook policy for all 51 tools.
Agents calling read-class tools like OUTLOOK_QUERY_EMAILS have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Primary tool for querying Outlook emails with custom OData filters. Build precise server-side filters for dates, read status, importance, subjects, attachments, and conversations. Best for structured queries on message metadata. Returns up to 100 messages per request with pagination support. • Server-side filters: dates, importance, isRead, hasAttachments, subjects, conversationId • CRITICAL: Always check response['@odata.nextLink'] for pagination • Limitations: Recipient/sender/category filters require OUTLOOK_SEARCH_MESSAGES • For keyword/body search: Use OUTLOOK_SEARCH_MESSAGES (KQL syntax). It is categorised as a Read tool in the Outlook MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for OUTLOOK_QUERY_EMAILS. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Outlook MCP server.
OUTLOOK_QUERY_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 OUTLOOK_QUERY_EMAILS rule in your Intercept 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 Intercept policy for OUTLOOK_QUERY_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.
OUTLOOK_QUERY_EMAILS is provided by the Outlook MCP server (outlook). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.