Get accessible custom fields in a list
AI agents call get-custom-fields to retrieve information from ClickUp Operator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about custom fields without modifying, creating, or deleting any data. It is a straightforward query operation that returns information about accessible custom fields. This poses minimal risk as it only exposes existing field definitions.
From the tool's definition The tool name is 'get-custom-fields' and the description states 'Get accessible custom fields in a list'. The verb 'Get' and the read-only nature of retrieving field metadata indicates this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get accessible custom fields in a list. It is categorised as a Read tool in the ClickUp Operator MCP Server, which means it retrieves data without modifying state.
Register the ClickUp Operator MCP server in PolicyLayer and add a rule for get-custom-fields: 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 Operator. Nothing to install.
get-custom-fields 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 get-custom-fields 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 get-custom-fields. 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.
get-custom-fields is provided by the ClickUp Operator MCP server (noah-vh/mcp-server-clickup). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →