Get full configuration of a list (statuses, defaults, etc)
AI agents call get_list_details to retrieve information from ClickUp MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata and configuration about a ClickUp list (statuses, defaults, etc.) without creating, modifying, or deleting any data. It is a straightforward data retrieval operation with no blast radius if misused by an AI agent—the worst outcome is exposure of configuration information already accessible to authorized users.
From the tool's definition Tool name 'get_list_details' and description 'Get full configuration of a list' indicate a retrieval operation with no side effects. The verb 'Get' and absence of any modification language confirm this is a read-only query.
Attacks that exploit this kind of access
Get full configuration of a list (statuses, defaults, etc). It is categorised as a Read tool in the ClickUp MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ClickUp MCP Server MCP server in PolicyLayer and add a rule for get_list_details: 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. Nothing to install.
get_list_details 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 get_list_details 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 get_list_details. 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.
get_list_details is provided by the ClickUp MCP Server MCP server (smeric28/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 →