remove_channel_members
Idempotently remove members from a non-archived Huly channel. Members accept account UUID, exact email, or exact person display name. Refuses removals that would leave the channel with zero members or, when owners exist, no owner among remaining members.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/remove-channel-members.md
What remove_channel_members does on Huly
AI agents call remove_channel_members to permanently remove resources in Huly, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_channel_members is rated Critical
Removing members from a channel is a destructive operation — once removed, their membership and access are revoked and must be manually re-added. There is no indication this is reversible or that a restore/undo mechanism exists. The blast radius is high because an AI agent could inadvertently remove critical members (including owners) from important communication channels, disrupting team collaboration.
From the tool's definition 'remove members from a non-archived Huly channel' — removing members is an irreversible action that changes channel membership, and the description notes it 'refuses removals that would leave the channel with zero members' implying real destructive…
Attacks that exploit this kind of access
The rule that runs remove_channel_members 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 remove_channel_members, this is the rule to start with:
remove_channel_members is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every remove_channel_members call is checked against it from then on.
Questions about remove_channel_members
Idempotently remove members from a non-archived Huly channel. Members accept account UUID, exact email, or exact person display name. Refuses removals that would leave the channel with zero members or, when owners exist, no owner among remaining members. It is categorised as a Destructive tool in the Huly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Huly MCP server in PolicyLayer and add a rule for remove_channel_members: 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.
remove_channel_members is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_channel_members 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 remove_channel_members. 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.
remove_channel_members 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.
Across the catalogue