clickup_get_custom_roles

A read tool on the Clickup MCP server.

SERVERClickup SOURCEtrustxai/clickup-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/clickup-mcp/clickup-get-custom-roles.md

WHAT IT DOES

What clickup_get_custom_roles does on Clickup

AI agents call clickup_get_custom_roles to retrieve information from Clickup without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why clickup_get_custom_roles is rated Low

The 'get' prefix is a standard indicator of read-only retrieval. Even with an empty description, the naming convention and context (managing custom roles in a task management system) suggest this fetches role definitions. No side effects, modifications, or deletions are implied.

From the tool's definition Tool name 'clickup_get_custom_roles' indicates a retrieval operation ('get'); description is empty but the name strongly suggests querying/fetching role data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clickup_get_custom_roles safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Clickup, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clickup_get_custom_roles, this is the rule to start with:

clickup_get_custom_roles Allowed

clickup_get_custom_roles is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clickup_get_custom_roles": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Clickup, apply this rule, and every clickup_get_custom_roles call is checked against it from then on.

FAQ

Questions about clickup_get_custom_roles

What does the clickup_get_custom_roles tool do? +

clickup_get_custom_roles is a read tool on the Clickup MCP server. 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 clickup_get_custom_roles? +

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

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

Can I rate-limit clickup_get_custom_roles? +

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

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

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

KEEP EXPLORING

More on Clickup, and thousands of servers like it.

This server

All 166 Clickup tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →