list_channels
List all Huly channels. Returns channels sorted by name. Supports filtering by archived status. Supports searching by name substring (nameSearch) and topic substring (topicSearch).
This record as markdown: /tools/dugynoo-huly-mcp/list-channels.md
What list_channels does on Huly
AI agents call list_channels 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_channels is rated Low
This tool retrieves and queries channel data with no side effects. It only returns existing information sorted and filtered by parameters, with no capability to create, modify, delete, or execute operations. Standard read operation with minimal security risk—information exposure depends on channel visibility permissions already enforced by the application.
From the tool's definition Tool description explicitly states 'List all Huly channels' with filtering and searching capabilities. The verb 'list' and absence of any modification, deletion, or execution language indicate a pure read operation.
Attacks that exploit this kind of access
The rule that runs list_channels 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_channels, this is the rule to start with:
list_channels 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_channels call is checked against it from then on.
Questions about list_channels
List all Huly channels. Returns channels sorted by name. Supports filtering by archived status. Supports searching by name substring (nameSearch) and topic substring (topicSearch). 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_channels: 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_channels 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_channels 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_channels. 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_channels 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.
This server
Across the catalogue