set_custom_field

Set a custom field value on a document. Requires the document ID, class, field ID (from list_custom_fields), and value. Values are auto-parsed: numbers from numeric strings, booleans from

SERVERHuly SOURCEdugynoo/huly-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dugynoo-huly-mcp/set-custom-field.md

What set_custom_field does on Huly

AI agents use set_custom_field to create or update resources in Huly, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huly environment.

Why set_custom_field is rated Medium

This tool creates or modifies data reversibly on a document object within the project management system. While it changes document state, the modification is not destructive (reversible via another set_custom_field call) and does not involve code execution or deletion. The severity is medium because misuse could corrupt document metadata or field values across the system, but changes remain reversible.

From the tool's definition Tool name 'set_custom_field' and description 'Set a custom field value on a document' indicates modification of data. The description explicitly states it requires document ID, class, field ID, and value parameters to update custom field values.

Questions about set_custom_field

What does the set_custom_field tool do? +

Set a custom field value on a document. Requires the document ID, class, field ID (from list_custom_fields), and value. Values are auto-parsed: numbers from numeric strings, booleans from. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_custom_field? +

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

set_custom_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_custom_field? +

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

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

set_custom_field 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.

// 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.