List accessible ClickUp workspaces (teams). Use when you need workspace IDs before exploring spaces.
AI agents call workspace_list to retrieve information from Clickup without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
forceRefresh | boolean | — | true to bypass cache and fetch from ClickUp. |
Parameters from the server's own tool schema.
This tool queries and returns a list of workspaces the user has access to. It performs no modifications, deletions, or executions. The primary use case is information discovery to obtain workspace identifiers for subsequent operations. This is a straightforward Read operation with minimal risk even if misused by an AI agent.
From the tool's definition Tool description explicitly states 'List accessible ClickUp workspaces' and 'when you need workspace IDs before exploring spaces' — a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access workspace_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Clickup, and nothing reaches the server without passing your rules. This is the rule we recommend for workspace_list:
{
"version": "1",
"default": "deny",
"tools": {
"workspace_list": {}
}
} workspace_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List accessible ClickUp workspaces (teams). Use when you need workspace IDs before exploring spaces. It is categorised as a Read tool in the Clickup MCP Server, which means it retrieves data without modifying state.
workspace_list accepts 1 parameter: forceRefresh. The full parameter table on this page comes from the server's own tool schema.
Register the Clickup MCP server in PolicyLayer and add a rule for workspace_list: 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.
workspace_list 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 workspace_list 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 workspace_list. 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.
workspace_list is provided by the Clickup MCP server (@taazkareem/clickup-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Clickup, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
41 Clickup tools catalogued and risk-classified — across an index of 43,000+ MCP servers.