Unified document management tool for ClickUp documents. DOCUMENT OPERATIONS: - create: Create new document in a container (space, folder, or list) - update: Update document properties (name, visibility) PARENT CONTAINER TYPES (for create action): - Type 4: Space - Type 5: Folder - Type 6: List (m...
AI agents use manage_document to create or update resources in ClickUp MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClickUp MCP environment.
manage_document enables creation and modification of ClickUp documents across various container types (spaces, folders, lists, workspaces). Creating and updating documents are Write operations—they create or reversibly modify data.
From the tool's definition Tool performs 'create' and 'update' operations on documents: 'Create new document in a container' and 'Update document properties (name, visibility)'. These are reversible modifications that create or alter data without deletion or destruction.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Unified document management tool for ClickUp documents. DOCUMENT OPERATIONS: - create: Create new document in a container (space, folder, or list) - update: Update document properties (name, visibility) PARENT CONTAINER TYPES (for create action): - Type 4: Space - Type 5: Folder - Type 6: List (most common) - Type 7: Everything - Type 12: Workspace DOCUMENT PROPERTIES: - name: Document title (required for create/update) - visibility:. It is categorised as a Write tool in the ClickUp MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ClickUp MCP server in PolicyLayer and add a rule for manage_document: 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. Nothing to install.
manage_document 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 manage_document 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 manage_document. 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.
manage_document is provided by the ClickUp MCP server (twofeetup/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 →