list_wecom_bots
AI agents call list_wecom_bots to retrieve information from WeCom Bot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' prefix strongly indicates a retrieval operation that queries and returns information about WeCom bots. While the description is uninformative, the pattern of sibling tools (all send/write operations) and the naming convention support classification as a Read operation. No data modification, deletion, or execution of commands occurs.
From the tool's definition Tool name 'list_wecom_bots' uses 'list' verb; description is empty but sibling tools are all send/write operations, suggesting this tool queries or enumerates existing bots without modifying state.
Attacks that exploit this kind of access
list_wecom_bots. It is categorised as a Read tool in the WeCom Bot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WeCom Bot MCP Server MCP server in PolicyLayer and add a rule for list_wecom_bots: 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 WeCom Bot MCP Server. Nothing to install.
list_wecom_bots 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_wecom_bots 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_wecom_bots. 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_wecom_bots is provided by the WeCom Bot MCP Server MCP server (loonghao/wecom-bot-mcp-server). 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 →