Lists dialogs tracked in the local archive registry.
AI agents call listActiveChannels to retrieve information from Telegram MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about channels from a local registry without creating, modifying, deleting, or executing any operations. It is a simple query that returns existing data. The low severity reflects minimal blast radius—an AI could list channels but cannot harm data or systems with this capability alone.
From the tool's definition Tool name 'listActiveChannels' and description 'Lists dialogs tracked in the local archive registry' indicate a retrieval operation with no side effects. The verb 'lists' and the context of querying archived channel metadata confirm read-only behavior.
Documented attack patterns abuse exactly the kind of access listActiveChannels gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for listActiveChannels:
{
"version": "1",
"default": "deny",
"tools": {
"listActiveChannels": {}
}
} listActiveChannels is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists dialogs tracked in the local archive registry. It is categorised as a Read tool in the Telegram MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Telegram MCP Server MCP server in PolicyLayer and add a rule for listActiveChannels: 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 Telegram MCP Server. Nothing to install.
listActiveChannels 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 listActiveChannels 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 listActiveChannels. 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.
listActiveChannels is provided by the Telegram MCP Server MCP server (kfastov/tgcli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Telegram MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
38 Telegram MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.