Create an item in a checklist
AI agents use create-checklist-item 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.
Creating a checklist item is a write operation—it adds new data to an existing checklist structure. This is reversible (the item can be deleted or modified later), so it does not qualify as Destructive. The blast radius is minimal: a checklist item can be easily removed or corrected, and it has no financial implications or code execution effects.
From the tool's definition Tool description states 'Create an item in a checklist', which is a create operation that modifies data (adding a new checklist item) in a reversible manner.
Attacks that exploit this kind of access
Create an item in a checklist. 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 create-checklist-item: 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.
create-checklist-item 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-checklist-item 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-checklist-item. 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-checklist-item 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 →