Medium Risk

time_report_for_container

Aggregate time for a workspace, space, folder or list using containerId + containerType. Resolve IDs with resolve_path_to_ids, list_workspaces/spaces/folders/lists, and set includeSubtasks to clarify hierarchy handling.

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

AI agents use time_report_for_container to create or modify resources in Clickup. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call time_report_for_container repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Clickup.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

clickup.yaml
tools:
  time_report_for_container:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Clickup policy for all 41 tools.

Tool Name time_report_for_container
Category Write
MCP Server Clickup MCP Server
Risk Level Medium

View all 41 tools →

Agents calling write-class tools like time_report_for_container 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 Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the time_report_for_container tool do? +

Aggregate time for a workspace, space, folder or list using containerId + containerType. Resolve IDs with resolve_path_to_ids, list_workspaces/spaces/folders/lists, and set includeSubtasks to clarify hierarchy handling.. It is categorised as a Write tool in the Clickup MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on time_report_for_container? +

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

What risk level is time_report_for_container? +

time_report_for_container is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit time_report_for_container? +

Yes. Add a rate_limit block to the time_report_for_container 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 time_report_for_container completely? +

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

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

Enforce policies on Clickup

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.