Get metadata and content for a specific attachment on an email message.
AI agents call outlook_get_attachment 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 and queries attachment data from email messages without side effects or state changes. It falls clearly under the Read category. Severity is medium rather than low because email attachments may contain sensitive information (PII, credentials, business secrets), so unauthorized retrieval could expose confidential data, but the tool itself does not execute code, modify data, or cause financial harm.
From the tool's definition Tool name is 'outlook_get_attachment' and description states it 'Get metadata and content for a specific attachment on an email message' — purely a retrieval operation with no modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access outlook_get_attachment 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_attachment:
{
"version": "1",
"default": "deny",
"tools": {
"outlook_get_attachment": {}
}
}outlook_get_attachment 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 metadata and content for a specific attachment on an email message. 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_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 Sage MCP. Nothing to install.
outlook_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 outlook_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 outlook_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.
outlook_get_attachment 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.