pt_list_channels

List the authenticated user

SERVERCrow SOURCEkh0pper/crow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/pt-list-channels.md

WHAT IT DOES

What pt_list_channels does on Crow

AI agents call pt_list_channels to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why pt_list_channels is rated Low

This tool retrieves information about channels or user data without modifying, deleting, or executing any operations. The description, while minimal, clearly indicates a listing/query function. The low severity reflects that information disclosure about channels has limited blast radius in a project management context, though confidence is slightly reduced due to the terse description.

From the tool's definition Tool name 'pt_list_channels' and description 'List the authenticated user' indicate a query/retrieval operation with no side effects. The verb 'List' is characteristic of Read category tools.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pt_list_channels safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pt_list_channels, this is the rule to start with:

pt_list_channels Allowed

pt_list_channels is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pt_list_channels": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about pt_list_channels

What does the pt_list_channels tool do? +

List the authenticated user. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pt_list_channels? +

Register the Crow MCP server in PolicyLayer and add a rule for pt_list_channels: 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 Crow. Nothing to install.

What risk level is pt_list_channels? +

pt_list_channels is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pt_list_channels? +

Yes. Add a rate_limit block to the pt_list_channels 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 pt_list_channels completely? +

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

pt_list_channels is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →