Deletes a contact. Disabled unless CLIO_ALLOW_DESTRUCTIVE=true. Returns 409 if the contact has
AI agents call clio_delete_contact to permanently remove resources in Clio Manage MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a contact permanently removes data that cannot be recovered through normal means. This is an irreversible action that destroys information, fitting the Destructive category. The fact that the developers require an explicit environment flag to enable it demonstrates awareness of its destructive nature.
From the tool's definition Tool name is 'clio_delete_contact' and description states 'Deletes a contact.' The description explicitly indicates this is a destructive operation by noting it is 'Disabled unless CLIO_ALLOW_DESTRUCTIVE=true', confirming the developers recognize it as…
Attacks that exploit this kind of access
Deletes a contact. Disabled unless CLIO_ALLOW_DESTRUCTIVE=true. Returns 409 if the contact has. It is categorised as a Destructive tool in the Clio Manage MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Clio Manage MCP server in PolicyLayer and add a rule for clio_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 Clio Manage MCP. Nothing to install.
clio_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 clio_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 clio_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.
clio_delete_contact is provided by the Clio Manage MCP server (patrickking67/clio-manage-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 →