Deletes a contact from the mailbox
AI agents call delete-contact to permanently remove resources in Outlook MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of contacts is an irreversible destructive action that cannot be undone. While the blast radius is scoped to a single contact rather than bulk data, this still represents permanent data loss. Severity is high rather than critical because it affects individual contact records rather than systemic financial, security, or organizational infrastructure.
From the tool's definition Tool name is 'delete-contact' and description states it 'Deletes a contact from the mailbox' — a permanent, irreversible removal of data.
Attacks that exploit this kind of access
Deletes a contact from the mailbox. It is categorised as a Destructive tool in the Outlook MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Outlook MCP Server MCP server in PolicyLayer and add a rule for delete-contact: 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 MCP Server. Nothing to install.
delete-contact 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 delete-contact 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 delete-contact. 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.
delete-contact is provided by the Outlook MCP Server MCP server (peacockery-studio/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 →