Critical Risk →

outlook_delete_email

Delete an email (move to Deleted Items or permanently delete)

How to control outlook_delete_email ↓

What outlook_delete_email does on Outlook

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

Critical Risk

Why outlook_delete_email needs a policy

This tool irreversibly deletes email data. Even though moving to Deleted Items may be reversible depending on retention policies, the tool explicitly includes permanent deletion capability, which cannot be undone. Destructive is the appropriate category per the severity hierarchy (Destructive > Execute > Write > Read).

From the tool's definition Tool description explicitly states 'Delete an email (move to Deleted Items or permanently delete)'. The capability to 'permanently delete' is irreversible data destruction.

Documented attack patterns abuse exactly the kind of access outlook_delete_email gives an agent:

How to control outlook_delete_email

PolicyLayer is an MCP gateway — it sits between your AI agents and Outlook, and nothing reaches the server without passing your rules. This is the rule we recommend for outlook_delete_email:

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

outlook_delete_email 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 Outlook — 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.

Related tools and policies

Go deeper

Questions about outlook_delete_email

What does the outlook_delete_email tool do? +

Delete an email (move to Deleted Items or permanently delete). It is categorised as a Destructive tool in the Outlook 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_email? +

Register the Outlook MCP server in PolicyLayer and add a rule for outlook_delete_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 Outlook. Nothing to install.

What risk level is outlook_delete_email? +

outlook_delete_email 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_email? +

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

How do I block outlook_delete_email completely? +

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

What MCP server provides outlook_delete_email? +

outlook_delete_email is provided by the Outlook MCP server (xenoxilus/outlook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Outlook tool call.

Start from Outlook, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

43 Outlook tools catalogued and risk-classified — across an index of 43,000+ 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.