Low Risk

get_workspace_tasks

Retrieve MULTIPLE tasks from workspace using broad filters. Returns full task details including description. Important: At least one filter must be provided: tags, list_ids, folder_ids, space_ids, statuses, assignees, date filters, custom_fields, custom_task_types, advanced_filtering/name_search,...

High parameter count (29 properties)

Part of the ClickUp MCP - Premium MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call get_workspace_tasks to retrieve information from ClickUp MCP - Premium 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 get_workspace_tasks 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.

taazkareem-clickup-mcp-premium.yaml
tools:
  get_workspace_tasks:
    rules:
      - action: allow

See the full ClickUp MCP - Premium policy for all 54 tools.

Tool Name get_workspace_tasks
Category Read
Risk Level Low

View all 54 tools →

Agents calling read-class tools like get_workspace_tasks have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the get_workspace_tasks tool do? +

Retrieve MULTIPLE tasks from workspace using broad filters. Returns full task details including description. Important: At least one filter must be provided: tags, list_ids, folder_ids, space_ids, statuses, assignees, date filters, custom_fields, custom_task_types, advanced_filtering/name_search, or search_query). It is categorised as a Read tool in the ClickUp MCP - Premium MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_workspace_tasks? +

Add a rule in your Intercept YAML policy under the tools section for get_workspace_tasks. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the ClickUp MCP - Premium MCP server.

What risk level is get_workspace_tasks? +

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

Can I rate-limit get_workspace_tasks? +

Yes. Add a rate_limit block to the get_workspace_tasks rule in your Intercept 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 get_workspace_tasks completely? +

Set action: deny in the Intercept policy for get_workspace_tasks. 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 get_workspace_tasks? +

get_workspace_tasks is provided by the ClickUp MCP - Premium MCP server (taazkareem/clickup-mcp-premium). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on ClickUp MCP - Premium

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.