New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_custom_field_values

Read custom field values from a document. Pass the document

SERVERHuly SOURCE@firfi/huly-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/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.

Questions about get_custom_field_values

What does the get_custom_field_values tool do? +

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.

How do I enforce a policy on get_custom_field_values? +

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.

What risk level is get_custom_field_values? +

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

Can I rate-limit get_custom_field_values? +

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.

How do I block get_custom_field_values completely? +

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.

What MCP server provides get_custom_field_values? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Huly's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.