Get a task by its custom ID
AI agents call clickup_get_task_by_custom_id 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 task data from ClickUp using a custom ID as the lookup parameter. It performs a query operation that reads existing data without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal — an AI agent could only retrieve task information the authenticated user already has access to, with no ability to alter, delete, or cause financial impact.
From the tool's definition Tool name contains 'get' and description states 'Get a task by its custom ID' — a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access clickup_get_task_by_custom_id 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 clickup_get_task_by_custom_id:
{
"version": "1",
"default": "deny",
"tools": {
"clickup_get_task_by_custom_id": {}
}
} clickup_get_task_by_custom_id 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 a task by its custom ID. 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 clickup_get_task_by_custom_id: 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.
clickup_get_task_by_custom_id 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 clickup_get_task_by_custom_id 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 clickup_get_task_by_custom_id. 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.
clickup_get_task_by_custom_id 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.