get_attachment
Get an email attachment's content (returned as base64 in contentBytes).
This record as markdown: /tools/0xka13b-microsoft-mcps/get-attachment.md
What get_attachment does on Microsoft MCP
AI agents call get_attachment 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 |
attachment_id | string | Yes | Attachment ID |
Parameters from the server's own tool schema.
Why get_attachment is rated Low
get_attachment fetches and returns existing data (an email attachment) without side effects. This is a Read operation. Severity is elevated to medium rather than low because attachments may contain sensitive data (credentials, PII, financial documents), and uncontrolled access could expose confidential information, though the attachment still exists after retrieval.
From the tool's definition The tool retrieves attachment content from emails, returning it as base64 data in contentBytes, with no modification or deletion of the source data.
Attacks that exploit this kind of access
The rule that runs get_attachment 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_attachment, this is the rule to start with:
get_attachment 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_attachment call is checked against it from then on.
Questions about get_attachment
Get an email attachment's content (returned as base64 in contentBytes). It is categorised as a Read tool in the Microsoft MCP MCP Server, which means it retrieves data without modifying state.
get_attachment accepts 2 parameters: email_id, attachment_id. Required: email_id, attachment_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_attachment: 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_attachment 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_attachment 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_attachment. 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_attachment 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