archive_channel

Archive a Huly channel by channel name or ID. This is reversible with unarchive_channel and is idempotent when the channel is already archived.

SERVERHuly SOURCE@firfi/huly-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dearlordylord-huly-mcp/archive-channel.md

WHAT IT DOES

What archive_channel does on Huly

AI agents use archive_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.

RISK

Why archive_channel is rated Medium

Archiving a channel modifies its state (mark as archived) but does not irreversibly delete data or make it inaccessible. The description explicitly notes reversibility via unarchive_channel, placing it in Write rather than Destructive. Medium severity reflects that an AI agent could archive important channels disrupting collaboration, but the action is recoverable.

From the tool's definition Tool description states it 'Archive[s] a Huly channel' and is 'reversible with unarchive_channel'. The reversibility and idempotent behavior distinguish it from Destructive actions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs archive_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 archive_channel, this is the rule to start with:

archive_channel Rate-limited

archive_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "archive_channel": {
      "limits": [
        {
          "counter": "archive_channel_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every archive_channel call is checked against it from then on.

FAQ

Questions about archive_channel

What does the archive_channel tool do? +

Archive a Huly channel by channel name or ID. This is reversible with unarchive_channel and is idempotent when the channel is already archived. 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.

How do I enforce a policy on archive_channel? +

Register the Huly MCP server in PolicyLayer and add a rule for archive_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.

What risk level is archive_channel? +

archive_channel is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit archive_channel? +

Yes. Add a rate_limit block to the archive_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.

How do I block archive_channel completely? +

Set action: deny in the PolicyLayer policy for archive_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.

What MCP server provides archive_channel? +

archive_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.

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 518 Huly tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →