This record as markdown: /tools/clickup-mcp/clickup-get-page.md
What clickup_get_page does on Clickup
AI agents call clickup_get_page 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_get_page is rated Low
This tool appears to retrieve a page (likely from ClickUp Docs). While the description is empty, the naming convention ('get' + object type) and the ClickUp context (which offers page/doc retrieval capabilities) strongly indicate this is a Read operation that queries data without modification.
From the tool's definition Tool name 'clickup_get_page' and ClickUp API context indicate a retrieval operation. The 'get' prefix and absence of mutation keywords (create, update, delete, etc.) suggest data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs clickup_get_page 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_get_page, this is the rule to start with:
clickup_get_page 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_get_page call is checked against it from then on.
Questions about clickup_get_page
clickup_get_page 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_get_page: 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_get_page 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_get_page 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_get_page. 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_get_page 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