Create a new tag on a workspace.
AI agents use create_tag to create or update resources in Clockify Time Tracking — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clockify Time Tracking environment.
Creating a tag is a write operation that adds metadata to organize time entries and projects. It is reversible (tags can be deleted or renamed) and has minimal blast radius. While the sibling tools include financial operations (invoice_item, invoice_payment) and destructive actions (archive), this particular tool only creates organizational metadata with no side effects on actual time data, finances, or system state.
From the tool's definition Tool creates a new tag on a workspace, which is a reversible data modification operation. The description explicitly states 'Create a new tag' indicating a write action.
Attacks that exploit this kind of access
Create a new tag on a workspace. It is categorised as a Write tool in the Clockify Time Tracking MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Clockify Time Tracking 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 Time Tracking. 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 Time Tracking MCP server (pypi:clockify-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 →