Delete a client by ID.
AI agents call delete_client to permanently remove resources in Mycase — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a client record from the MyCase system, which cannot be undone. Deletion of client data in a legal practice management system is irreversible and could have serious consequences for case management, client relationships, and compliance. This is the most severe category (Destructive) rather than Write, as it destroys data rather than modifying it reversibly.
From the tool's definition Tool name is 'delete_client' and description states 'Delete a client by ID.' The verb 'delete' combined with the irreversible nature of removing a client record from a law firm's case management system makes this a destructive operation.
Attacks that exploit this kind of access
Delete a client by ID. It is categorised as a Destructive tool in the Mycase MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mycase MCP server in PolicyLayer and add a rule for delete_client: 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 Mycase. Nothing to install.
delete_client 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 delete_client 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 delete_client. 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.
delete_client is provided by the Mycase MCP server (rosenadvertising/mycase-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 →