delete_contact

Archive or delete a contact in Sanka or a connected CRM by contact id or external reference.

Server Sanka MCP Server sankahq/sanka-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_contact does on Sanka MCP Server

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

Why delete_contact needs a policy

This tool performs an irreversible deletion operation on contact records. Although 'archive' may be reversible depending on implementation, the inclusion of 'delete' in the description indicates capability for permanent data removal. Contact deletion is destructive because it removes business-critical customer/contact information that typically cannot be undone.

From the tool's definition Tool description explicitly states 'delete a contact' and 'Archive or delete', indicating irreversible removal of contact data. The phrase 'delete' combined with contact management context means data cannot be recovered through normal operations.

Questions about delete_contact

What does the delete_contact tool do? +

Archive or delete a contact in Sanka or a connected CRM by contact id or external reference. It is categorised as a Destructive tool in the Sanka MCP Server 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 Sanka 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 Sanka MCP Server. 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 Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.