get_custom_field_values
Read custom field values from a document. Pass the document
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/get-custom-field-values.md
What get_custom_field_values does on Huly
AI agents call get_custom_field_values 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 get_custom_field_values is rated Low
This tool queries and retrieves custom field values without side effects. It performs a straightforward read operation on document metadata. There is no creation, modification, deletion, or execution of code. The low severity reflects that misuse would only expose data already accessible within the Huly system, with no destructive or financial impact.
From the tool's definition Tool description explicitly states "Read custom field values from a document." The verb "Read" and the retrieval-only nature (no modification, deletion, or execution) clearly indicate this is a data retrieval operation.
Attacks that exploit this kind of access
The rule that runs get_custom_field_values 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 get_custom_field_values, this is the rule to start with:
get_custom_field_values 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 get_custom_field_values call is checked against it from then on.
Questions about get_custom_field_values
Read custom field values from a document. Pass the document. 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 get_custom_field_values: 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.
get_custom_field_values 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_field_values 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_field_values. 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_field_values is provided by the Huly MCP server (@firfi/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