Critical Risk →

delete_client

Delete a client

How to control delete_client ↓

What delete_client does on Clockify MCP Server

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

Critical Risk

Why delete_client needs a policy

Deleting a client is an irreversible action that cannot be undone and will remove associated data from the time tracking system. This constitutes a destructive operation.

From the tool's definition Tool name 'delete_client' with description 'Delete a client' indicates irreversible deletion of a client record.

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

How to control delete_client

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

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

delete_client 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 Clockify MCP Server — 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 delete_client

What does the delete_client tool do? +

Delete a client. It is categorised as a Destructive tool in the Clockify 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_client? +

Register the Clockify MCP Server 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 Clockify MCP Server. Nothing to install.

What risk level is delete_client? +

delete_client 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_client? +

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.

How do I block delete_client completely? +

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.

What MCP server provides delete_client? +

delete_client is provided by the Clockify MCP Server MCP server (ratheesh-aot/clockify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Clockify MCP Server tool call.

Start from Clockify MCP Server, 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.

29 Clockify MCP Server 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.