AI agents call get_spaces to retrieve information from ClickUp MCP Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves organizational metadata (spaces) from ClickUp but does not create, modify, delete, or execute any operations. It is a straightforward data query with no blast radius if misused by an AI agent—the worst outcome would be unnecessary API calls or information disclosure of workspace structure the user likely already has access to.
From the tool's definition Tool name 'get_spaces' and description 'Get all spaces in the workspace' indicate a retrieval operation that queries workspace structure without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_spaces gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ClickUp MCP Integration, and nothing reaches the server without passing your rules. This is the rule we recommend for get_spaces:
{
"version": "1",
"default": "deny",
"tools": {
"get_spaces": {}
}
}get_spaces 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.
Get all spaces in the workspace. It is categorised as a Read tool in the ClickUp MCP Integration MCP Server, which means it retrieves data without modifying state.
Register the ClickUp MCP Integration MCP server in PolicyLayer and add a rule for get_spaces: 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 Integration. Nothing to install.
get_spaces 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_spaces 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_spaces. 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_spaces is provided by the ClickUp MCP Integration MCP server (leanware-io/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 MCP Integration, 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.
20 ClickUp MCP Integration tools catalogued and risk-classified — across an index of 43,000+ MCP servers.