list_message_template_fields
List Huly message template fields/placeholders without executing provider resources or rendering templates. Optionally filter by field category ID or exact raw label string, and search raw field labels by substring. Returns field IDs, labels, category summaries, and provider resource IDs.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-message-template-fields.md
What list_message_template_fields does on Huly
AI agents call list_message_template_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_message_template_fields is rated Low
The tool retrieves and lists metadata about message template fields—it reads existing configuration data without modifying, deleting, executing code, or triggering external operations. The explicit mention that it does NOT execute provider resources or render templates confirms this is a read-only query operation.
From the tool's definition Tool description explicitly states it 'List[s]' fields and 'Returns field IDs, labels, category summaries, and provider resource IDs' without 'executing provider resources or rendering templates'. This is a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_message_template_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_message_template_fields, this is the rule to start with:
list_message_template_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_message_template_fields call is checked against it from then on.
Questions about list_message_template_fields
List Huly message template fields/placeholders without executing provider resources or rendering templates. Optionally filter by field category ID or exact raw label string, and search raw field labels by substring. Returns field IDs, labels, category summaries, and provider resource IDs. 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_message_template_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_message_template_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_message_template_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_message_template_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_message_template_fields 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