list_huly_plugin_configurations
List read-only Huly plugin configuration records from core.class.PluginConfiguration. Returns plugin id, label, enabled/beta flags, and transaction count so an LLM can see installed model plugin gates without mutating configuration.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-huly-plugin-configurations.md
What list_huly_plugin_configurations does on Huly
AI agents call list_huly_plugin_configurations 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_huly_plugin_configurations is rated Low
This tool retrieves and queries plugin configuration data without any ability to modify, delete, or execute operations. The explicit "read-only" designation and emphasis on "without mutating configuration" confirm it has no side effects. It is purely informational retrieval, placing it in the Read category with low severity.
From the tool's definition Tool is explicitly described as "List read-only Huly plugin configuration records" with the stated purpose of letting "an LLM can see installed model plugin gates without mutating configuration." It returns metadata (plugin id, label, enabled/beta flags,…
Attacks that exploit this kind of access
The rule that runs list_huly_plugin_configurations 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_huly_plugin_configurations, this is the rule to start with:
list_huly_plugin_configurations 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_huly_plugin_configurations call is checked against it from then on.
Questions about list_huly_plugin_configurations
List read-only Huly plugin configuration records from core.class.PluginConfiguration. Returns plugin id, label, enabled/beta flags, and transaction count so an LLM can see installed model plugin gates without mutating configuration. 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_huly_plugin_configurations: 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_huly_plugin_configurations 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_huly_plugin_configurations 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_huly_plugin_configurations. 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_huly_plugin_configurations 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