Add tags to time entries
AI agents use add-tags-to-time-entries to create or update resources in ClickUp Operator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClickUp Operator environment.
Adding tags to time entries is a write operation that modifies data (tags) associated with time entries. It is reversible since tags can be removed. The severity is medium because misuse could corrupt time tracking metadata or add misleading tags to work records, affecting data quality and project visibility, but would not cause financial loss or irreversible deletion.
From the tool's definition Tool name 'add-tags-to-time-entries' and description 'Add tags to time entries' indicate the tool modifies metadata of existing time entries by adding tags. This is a reversible modification operation.
Attacks that exploit this kind of access
Add tags to time entries. It is categorised as a Write tool in the ClickUp Operator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ClickUp Operator MCP server in PolicyLayer and add a rule for add-tags-to-time-entries: 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 ClickUp Operator. Nothing to install.
add-tags-to-time-entries 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 add-tags-to-time-entries 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 add-tags-to-time-entries. 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.
add-tags-to-time-entries is provided by the ClickUp Operator MCP server (noah-vh/mcp-server-clickup). 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 →