clickup_move_attachment
Move an attachment to another parent object (task, comment, doc, or chat).
This record as markdown: /tools/chykalophia-clickup-mcp-server-enhanced/clickup-move-attachment.md
What clickup_move_attachment does on ClickUp MCP Server - Enhanced
AI agents use clickup_move_attachment to create or update resources in ClickUp MCP Server - Enhanced, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClickUp MCP Server - Enhanced environment.
Why clickup_move_attachment is rated Medium
Moving an attachment changes its parent association but does not delete or create new data in a destructive sense. The operation is reversible (can be moved back), making it a Write category tool rather than Destructive.
From the tool's definition Tool description states it 'Move[s] an attachment to another parent object (task, comment, doc, or chat)' - this modifies the location/association of an attachment, which is a reversible data modification operation.
Attacks that exploit this kind of access
The rule that runs clickup_move_attachment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ClickUp MCP Server - Enhanced, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clickup_move_attachment, this is the rule to start with:
clickup_move_attachment stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ClickUp MCP Server - Enhanced, apply this rule, and every clickup_move_attachment call is checked against it from then on.
Questions about clickup_move_attachment
Move an attachment to another parent object (task, comment, doc, or chat). It is categorised as a Write tool in the ClickUp MCP Server - Enhanced MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ClickUp MCP Server - Enhanced MCP server in PolicyLayer and add a rule for clickup_move_attachment: 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 - Enhanced. Nothing to install.
clickup_move_attachment 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 clickup_move_attachment 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 clickup_move_attachment. 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.
clickup_move_attachment is provided by the ClickUp MCP Server - Enhanced MCP server (chykalophia/clickup-mcp-server---enhanced). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ClickUp MCP Server - Enhanced, and thousands of servers like it.
This server
Across the catalogue