channel_list_chats

List recently active chats for a given messaging channel (from the local gateway message log).

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

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/cowork-os/channel-list-chats.md

WHAT IT DOES

What channel_list_chats does on CoWork OS

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

RISK

Why channel_list_chats is rated Low

This tool retrieves or queries chat history data from a local message log without creating, modifying, deleting, or executing operations. It is a straightforward read-only information retrieval function with minimal security impact.

From the tool's definition Tool name contains 'list' and description explicitly states 'List recently active chats' with qualifier 'from the local gateway message log', indicating a retrieval operation with no modification or destructive capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs channel_list_chats safely

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

channel_list_chats Allowed

channel_list_chats 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": {
    "channel_list_chats": {}
  }
}

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

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

FAQ

Questions about channel_list_chats

What does the channel_list_chats tool do? +

List recently active chats for a given messaging channel (from the local gateway message log). It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on channel_list_chats? +

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

What risk level is channel_list_chats? +

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

Can I rate-limit channel_list_chats? +

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

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

channel_list_chats is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →search_channel on YouTube 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 →