Critical Risk →

clio_delete_matter

clio_delete_matter

How to control clio_delete_matter ↓

What clio_delete_matter does on Clio

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

Critical Risk

Why clio_delete_matter needs a policy

Deletion of legal matters is a destructive operation that cannot be undone and removes critical business data. The blast radius is high as a legal matter typically contains years of work, client information, financial records, and case history. Even without explicit description, the 'delete' verb combined with 'matter' (core legal practice data) clearly indicates destructive capability.

From the tool's definition Tool name is 'clio_delete_matter' with no description provided. The verb 'delete' indicates irreversible removal of a matter (case/legal engagement) from Clio Manage.

Documented attack patterns abuse exactly the kind of access clio_delete_matter gives an agent:

How to control clio_delete_matter

PolicyLayer is an MCP gateway — it sits between your AI agents and Clio, and nothing reaches the server without passing your rules. This is the rule we recommend for clio_delete_matter:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "clio_delete_matter"
  ]
}

clio_delete_matter disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Clio — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about clio_delete_matter

What does the clio_delete_matter tool do? +

clio_delete_matter. It is categorised as a Destructive tool in the Clio 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 clio_delete_matter? +

Register the Clio MCP server in PolicyLayer and add a rule for clio_delete_matter: 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. Nothing to install.

What risk level is clio_delete_matter? +

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

Yes. Add a rate_limit block to the clio_delete_matter 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 clio_delete_matter completely? +

Set action: deny in the PolicyLayer policy for clio_delete_matter. 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 clio_delete_matter? +

clio_delete_matter is provided by the Clio MCP server (lawyered0/clio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Clio tool call.

Start from Clio, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

10 Clio tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.