Critical Risk →

outlook_delete_message

Delete an email message. Moves to Deleted Items folder.

How to control outlook_delete_message ↓

AI agents call outlook_delete_message to permanently remove resources in Sage MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Deleting email messages is an irreversible action in practical terms—users cannot recover deleted messages through normal means, and an AI agent with access to this tool could delete important communications, business records, or evidence. This constitutes data destruction and matches the Destructive category definition.

From the tool's definition Tool name contains 'delete' and description states 'Delete an email message.' The action moves messages to a Deleted Items folder, which is functionally permanent deletion from the user's active mailbox.

Documented attack patterns abuse exactly the kind of access outlook_delete_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_delete_message:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "outlook_delete_message"
  ]
}

outlook_delete_message disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Sage MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the outlook_delete_message tool do? +

Delete an email message. Moves to Deleted Items folder. It is categorised as a Destructive tool in the Sage MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on outlook_delete_message? +

Register the Sage MCP server in PolicyLayer and add a rule for outlook_delete_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_delete_message? +

outlook_delete_message is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit outlook_delete_message? +

Yes. Add a rate_limit block to the outlook_delete_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_delete_message completely? +

Set action: deny in the PolicyLayer policy for outlook_delete_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_delete_message? +

outlook_delete_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.

Enforce policy on every Sage MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.