Create a list in a folder
AI agents use create_list_in_folder to create or update resources in ClickUp MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClickUp MCP Server environment.
This tool creates new data (a list) within an existing folder structure. Creation is a reversible operation (lists can be deleted), so it falls under Write rather than Destructive or Execute. The severity is medium because creating lists could clutter a workspace or be used to add unauthorized organizational elements, but the impact is contained to organizational metadata and reversible.
From the tool's definition Tool name is 'create_list_in_folder' and description states 'Create a list in a folder' — this creates a new organizational structure within ClickUp that is reversible through deletion.
Attacks that exploit this kind of access
Create a list in a folder. It is categorised as a Write tool in the ClickUp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ClickUp MCP Server MCP server in PolicyLayer and add a rule for create_list_in_folder: 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 MCP Server. Nothing to install.
create_list_in_folder 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_list_in_folder 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_list_in_folder. 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_list_in_folder is provided by the ClickUp MCP Server MCP server (smeric28/clickup-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 →