clickup_replace_time_estimates_by_user
A write tool on the Clickup MCP server.
This record as markdown: /tools/clickup-mcp/clickup-replace-time-estimates-by-user.md
What clickup_replace_time_estimates_by_user does on Clickup
AI agents use clickup_replace_time_estimates_by_user to create or update resources in Clickup, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clickup environment.
Why clickup_replace_time_estimates_by_user is rated Medium
The 'replace' verb indicates this tool modifies time estimate data for a user, which is a reversible write operation. While potentially disruptive if misapplied (e.g., zeroing out all estimates), the action is not destructive (can be undone) and affects operational metadata rather than core task data. Medium severity reflects the operational impact on project planning without being irreversible.
From the tool's definition Tool name 'clickup_replace_time_estimates_by_user' contains 'replace', indicating modification of existing data (time estimates). Description is empty, limiting specificity.
Attacks that exploit this kind of access
The rule that runs clickup_replace_time_estimates_by_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Clickup, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clickup_replace_time_estimates_by_user, this is the rule to start with:
clickup_replace_time_estimates_by_user 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, apply this rule, and every clickup_replace_time_estimates_by_user call is checked against it from then on.
Questions about clickup_replace_time_estimates_by_user
clickup_replace_time_estimates_by_user is a write tool on the Clickup MCP server. It is categorised as a Write tool in the Clickup 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 clickup_replace_time_estimates_by_user: 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. Nothing to install.
clickup_replace_time_estimates_by_user 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_replace_time_estimates_by_user 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_replace_time_estimates_by_user. 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_replace_time_estimates_by_user is provided by the Clickup MCP server (trustxai/clickup-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Clickup, and thousands of servers like it.
This server
Across the catalogue