list_custom_fields
List custom field definitions in the workspace. Returns fields with their labels, types, and owner class info. Custom fields are created in the Huly UI on Card types, Issue types, or other classes. Use targetClass to filter fields for a specific class.
This record as markdown: /tools/dugynoo-huly-mcp/list-custom-fields.md
What list_custom_fields does on Huly
AI agents call list_custom_fields to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_custom_fields is rated Low
This tool queries and returns metadata about custom fields without modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves existing configuration data from the workspace. The use of 'List' and 'Returns' confirms data retrieval semantics. Severity is low because exposure of field definitions poses minimal risk to the system.
From the tool's definition Tool name 'list_custom_fields' and description stating it 'List[s] custom field definitions' and 'Returns fields with their labels, types, and owner class info.' This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_custom_fields safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_custom_fields, this is the rule to start with:
list_custom_fields is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every list_custom_fields call is checked against it from then on.
Questions about list_custom_fields
List custom field definitions in the workspace. Returns fields with their labels, types, and owner class info. Custom fields are created in the Huly UI on Card types, Issue types, or other classes. Use targetClass to filter fields for a specific class. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly MCP server in PolicyLayer and add a rule for list_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 Huly. Nothing to install.
list_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 list_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 list_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.
list_custom_fields is provided by the Huly MCP server (dugynoo/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue