delete_tag

THE RISK

Critical Risk

Why delete_tag needs a policy

This tool deletes a tag, which is an irreversible operation that cannot be undone. While the blast radius is limited (deletion of a single tag, not financial data or critical system operations), it still falls into the Destructive category as it permanently removes data.

From the tool's definition Tool name is 'delete_tag' with description 'Delete a tag'. The verb 'delete' indicates irreversible removal of data.

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

POLICY

How to control delete_tag

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_tag:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_tag"
  ]
}

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

Create a free account and register Clockify MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Clockify MCP Server tools

Destructive delete_client Delete a client Destructive delete_project Delete a project Destructive delete_task Delete a task Destructive delete_time_entry Delete a time entry Write stop_time_entry Stop a running time entry Write duplicate_time_entry Duplicate a time entry Write create_client Create a new client Write create_project Create a new project

All 29 Clockify MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Clockify MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_tag

What does the delete_tag tool do? +

Delete a tag. 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_tag? +

Register the Clockify MCP Server MCP server in PolicyLayer and add a rule for delete_tag: 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_tag? +

delete_tag 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_tag? +

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

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

delete_tag 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.

CHECK YOUR STACK →