join_channel
Join a non-archived Huly channel as the authenticated account. Idempotent when the account is already a member.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/join-channel.md
What join_channel does on Huly
AI agents use join_channel 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 join_channel is rated Medium
Joining a channel modifies membership state (adds the authenticated user to a channel), which is a reversible write operation. It is not destructive, financial, or executing code. Severity is medium because it changes access/membership state but is idempotent and reversible.
From the tool's definition Join a non-archived Huly channel as the authenticated account. Idempotent when the account is already a member.
Attacks that exploit this kind of access
The rule that runs join_channel 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 join_channel, this is the rule to start with:
join_channel stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 join_channel call is checked against it from then on.
Questions about join_channel
Join a non-archived Huly channel as the authenticated account. Idempotent when the account is already a member. 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.
Register the Huly MCP server in PolicyLayer and add a rule for join_channel: 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.
join_channel is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the join_channel 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 join_channel. 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.
join_channel 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