get_email
Get a single email message by ID with full body and headers.
This record as markdown: /tools/0xka13b-microsoft-mcps/get-email.md
What get_email does on Microsoft MCP
AI agents call get_email 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 |
|---|---|---|---|
email_id | string | Yes | Message ID |
include_body | boolean | — | Include message body. Defaults to true. |
body_max_length | integer | — | Max characters of body content to return. Defaults to 50000. |
include_attachments | boolean | — | Include attachment metadata. Defaults to true. |
Parameters from the server's own tool schema.
Why get_email is rated Low
This tool retrieves a single email message by its ID, returning the full body and headers. It performs no side effects, creates no new data, executes no code, deletes nothing, and involves no financial transactions. It is a straightforward read operation querying an existing resource.
From the tool's definition Tool name is 'get_email' and description states 'Get a single email message by ID with full body and headers.' The verb 'Get' and the description clearly indicate retrieval of existing data without modification or deletion.
Attacks that exploit this kind of access
The rule that runs get_email 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 get_email, this is the rule to start with:
get_email 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 get_email call is checked against it from then on.
Questions about get_email
Get a single email message by ID with full body and headers. It is categorised as a Read tool in the Microsoft MCP MCP Server, which means it retrieves data without modifying state.
get_email accepts 4 parameters: email_id, include_body, body_max_length, include_attachments. Required: email_id. 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 get_email: 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.
get_email 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 get_email 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 get_email. 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.
get_email 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