remove_organization_channel
Remove one contact channel from an organization identified by ID or exact unique name. Identify the channel with exactly one locator: channelId, or provider plus value. Returns removed=false when the locator is absent for that organization.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/remove-organization-channel.md
What remove_organization_channel does on Huly
AI agents call remove_organization_channel 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_organization_channel is rated Critical
This tool irreversibly deletes contact channel data from an organization. Removing a communication channel cannot be undone without manual restoration, and the loss of contact information could disrupt business operations. This is more severe than a Write operation (which is reversible) and constitutes a Destructive action.
From the tool's definition Tool name 'remove_organization_channel' and description phrase 'Remove one contact channel from an organization' — the verb 'remove' combined with the inability to undo deletion of a contact channel (permanent data loss) qualifies as destructive.
Attacks that exploit this kind of access
The rule that runs remove_organization_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 remove_organization_channel, this is the rule to start with:
remove_organization_channel 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_organization_channel call is checked against it from then on.
Questions about remove_organization_channel
Remove one contact channel from an organization identified by ID or exact unique name. Identify the channel with exactly one locator: channelId, or provider plus value. Returns removed=false when the locator is absent for that organization. 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_organization_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.
remove_organization_channel 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_organization_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 remove_organization_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.
remove_organization_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.
Across the catalogue