Critical Risk →

OUTLOOK_DELETE_CONTACT

Permanently deletes an existing contact, using its `contact_id` (obtainable via 'List User Contacts' or 'Get Contact'), from the Outlook contacts of the user specified by `user_id`.

Part of the Outlook MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

outlook Destructive

AI agents may call OUTLOOK_DELETE_CONTACT to permanently remove or destroy resources in Outlook. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call OUTLOOK_DELETE_CONTACT in a loop, permanently destroying resources in Outlook. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

outlook.yaml
tools:
  OUTLOOK_DELETE_CONTACT:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Outlook policy for all 51 tools.

Tool Name OUTLOOK_DELETE_CONTACT
Category Destructive
MCP Server Outlook MCP Server
Risk Level Critical

View all 51 tools →

Agents calling destructive-class tools like OUTLOOK_DELETE_CONTACT have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

OUTLOOK_DELETE_CONTACT is one of the critical-risk operations in Outlook. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the OUTLOOK_DELETE_CONTACT tool do? +

Permanently deletes an existing contact, using its `contact_id` (obtainable via 'List User Contacts' or 'Get Contact'), from the Outlook contacts of the user specified by `user_id`.. 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_CONTACT? +

Add a rule in your Intercept YAML policy under the tools section for OUTLOOK_DELETE_CONTACT. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Outlook MCP server.

What risk level is OUTLOOK_DELETE_CONTACT? +

OUTLOOK_DELETE_CONTACT 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_CONTACT? +

Yes. Add a rate_limit block to the OUTLOOK_DELETE_CONTACT rule in your Intercept 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_CONTACT completely? +

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

What MCP server provides OUTLOOK_DELETE_CONTACT? +

OUTLOOK_DELETE_CONTACT is provided by the Outlook MCP server (outlook). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.