Batch delete messages.
AI agents call deleteMessages 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.
Deletion of messages is an irreversible operation that cannot be undone through the API. Batch deletion amplifies the blast radius by allowing multiple messages to be destroyed in one call. Even if a user has a recoverable trash/deleted items folder in Outlook, the tool's effect is to remove messages from the primary view and make them unavailable for normal operations.
From the tool's definition Tool name is 'deleteMessages' and description states 'Batch delete messages.' The word 'delete' combined with 'batch' operation indicates irreversible removal of email data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Batch delete messages. 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.
Register the Outlook MCP server in PolicyLayer and add a rule for deleteMessages: 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.
deleteMessages is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteMessages 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 deleteMessages. 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.
deleteMessages is provided by the Outlook MCP server (lihaokun/outlook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →