Low Risk

folder_list_for_space

List folders within a ClickUp space. Use when you already know spaceId.

Part of the Clickup server.

folder_list_for_space is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE CLICKUP →

Free to start. No card required.

AI agents call folder_list_for_space to retrieve information from Clickup without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though folder_list_for_space only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "folder_list_for_space": {}
  }
}

See the full Clickup policy for all 41 tools.

Get this rule live on your own Clickup server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CLICKUP →

View all 41 tools →

These attack patterns abuse exactly the kind of access folder_list_for_space gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so folder_list_for_space only ever does what you allow.

SECURE CLICKUP →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the folder_list_for_space tool do? +

List folders within a ClickUp space. Use when you already know spaceId.. It is categorised as a Read tool in the Clickup MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on folder_list_for_space? +

Register the Clickup MCP server in PolicyLayer and add a rule for folder_list_for_space: 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.

What risk level is folder_list_for_space? +

folder_list_for_space is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit folder_list_for_space? +

Yes. Add a rate_limit block to the folder_list_for_space 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.

How do I block folder_list_for_space completely? +

Set action: deny in the PolicyLayer policy for folder_list_for_space. 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.

What MCP server provides folder_list_for_space? +

folder_list_for_space 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.

Enforce policy on every Clickup tool call.

Deterministic rules across all 41 Clickup tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.