outlook_get_message

Get a specific email message by its ID, including full body content and metadata.

SERVERSage MCP SOURCEsagemcp/sagemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/outlook-get-message.md

WHAT IT DOES

What outlook_get_message does on Sage MCP

AI agents call outlook_get_message 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.

RISK

Why outlook_get_message is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs outlook_get_message 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_get_message, this is the rule to start with:

outlook_get_message Allowed

outlook_get_message is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "outlook_get_message": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every outlook_get_message call is checked against it from then on.

FAQ

Questions about outlook_get_message

What does the outlook_get_message tool do? +

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.

How do I enforce a policy on outlook_get_message? +

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.

What risk level is outlook_get_message? +

outlook_get_message is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit outlook_get_message? +

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.

How do I block outlook_get_message completely? +

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.

What MCP server provides outlook_get_message? +

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.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →