delete_contact

Delete a contact by ID. This action is permanent.

SERVERIconnect SOURCEiconnect-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/delete-contact.md

WHAT IT DOES

What delete_contact does on Iconnect

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

RISK

Why delete_contact is rated Critical

This tool irreversibly removes contact data without possibility of recovery. While the blast radius is limited to personal contact records rather than financial or system-wide data, the permanent nature of deletion and potential for unintended removal of important contact information (phone numbers, emails, addresses) justifies 'Destructive' category and 'high' severity.

From the tool's definition Tool description explicitly states: 'Delete a contact by ID. This action is permanent.' The verb 'delete' combined with 'permanent' confirms irreversible data removal.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_contact safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_contact, this is the rule to start with:

delete_contact Hidden

delete_contact is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_contact"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every delete_contact call is checked against it from then on.

FAQ

Questions about delete_contact

What does the delete_contact tool do? +

Delete a contact by ID. This action is permanent. It is categorised as a Destructive tool in the Iconnect 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 delete_contact? +

Register the Iconnect 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 Iconnect. Nothing to install.

What risk level is delete_contact? +

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 delete_contact? +

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.

How do I block delete_contact completely? +

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.

What MCP server provides delete_contact? +

delete_contact is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →