获取群聊列表
AI agents call list_chatrooms to retrieve information from Chatlog 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 or enumerates chatroom data with no side effects. It is a straightforward listing operation consistent with the Read category. The low severity reflects minimal risk—an agent listing chatrooms cannot cause data loss, execute code, or trigger external operations. Confidence is high based on clear naming and the sibling context (get_chatlog, list_contacts, list_sessions are all Read-type tools).
From the tool's definition Tool name 'list_chatrooms' and description '获取群聊列表' (Chinese: 'Get group chat list') indicate a query/retrieval operation that lists available chatrooms without modification.
Attacks that exploit this kind of access
获取群聊列表. It is categorised as a Read tool in the Chatlog MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chatlog MCP Server MCP server in PolicyLayer and add a rule for list_chatrooms: 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 Chatlog MCP Server. Nothing to install.
list_chatrooms 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 list_chatrooms 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 list_chatrooms. 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.
list_chatrooms is provided by the Chatlog MCP Server MCP server (yhai3596/mcp-chatlog). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →