Get a specific email message by its ID, including full body content and metadata.
AI agents call outlook_get_message to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves email content and metadata by ID. It performs a read-only query operation with no side effects—it does not create, modify, delete, or execute any actions. The primary risk is information disclosure if unauthorized access occurs, but the tool itself is a simple data retrieval function.
From the tool's definition Tool name 'outlook_get_message' and description 'Get a specific email message by its ID, including full body content and metadata' indicate retrieval of email data without modification or deletion.
Documented attack patterns abuse exactly the kind of access outlook_get_message gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for outlook_get_message:
{
"version": "1",
"default": "deny",
"tools": {
"outlook_get_message": {}
}
}outlook_get_message is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a specific email message by its ID, including full body content and metadata. 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_get_message: 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_get_message 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_get_message 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_get_message. 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_get_message 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.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.