clickup_health_check
A read tool on the Clickup MCP server.
This record as markdown: /tools/clickup-mcp/clickup-health-check.md
What clickup_health_check does on Clickup
AI agents call clickup_health_check to retrieve information from Clickup without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why clickup_health_check is rated Low
Health checks are non-destructive operations that query service status and availability. They do not create, modify, delete, or execute arbitrary operations—they simply retrieve diagnostic information. The empty description reduces confidence slightly, but the tool name is sufficiently explicit. The low severity reflects minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'clickup_health_check' strongly suggests a status/diagnostic query operation. The naming convention is consistent with Read operations (e.g., 'check', 'status', 'health') that verify system state without modification.
Attacks that exploit this kind of access
The rule that runs clickup_health_check 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_health_check, this is the rule to start with:
clickup_health_check is read-only, so it stays allowed. 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_health_check call is checked against it from then on.
Questions about clickup_health_check
clickup_health_check is a read tool on the Clickup MCP server. It is categorised as a Read tool in the Clickup MCP Server, which means it retrieves data without modifying state.
Register the Clickup MCP server in PolicyLayer and add a rule for clickup_health_check: 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_health_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the clickup_health_check 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_health_check. 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_health_check 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