AI agents use create_tag to create or update resources in Clockify MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clockify MCP Server environment.
Creating a tag is a reversible, non-destructive write operation. It adds metadata to the time-tracking system without modifying or deleting existing data. The blast radius is minimal—incorrect tags can be deleted or ignored. This does not execute external code, move money, or irreversibly destroy data.
From the tool's definition Tool name 'create_tag' and description 'Create a new tag' indicate a data creation operation. The Clockify API context shows this creates a new tag entity in the time-tracking system.
Documented attack patterns abuse exactly the kind of access create_tag gives an agent:
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 create_tag:
{
"version": "1",
"default": "deny",
"tools": {
"create_tag": {
"limits": [
{
"counter": "create_tag_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_tag stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new tag. It is categorised as a Write tool in the Clockify MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Clockify MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_tag is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
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.