AI agents call get_chat_history to retrieve information from WeChat 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 encrypted chat history, sessions, and contact data from a local WeChat database. While categorized as Read (retrieval only, no modifications), it warrants high severity because: (1) it accesses sensitive personal communication data, (2) chat histories often contain private, confidential, or compromising information, (3) an AI agent with unrestricted access could exfiltrate large volumes of…
From the tool's definition Tool description indicates it 'retrieves...chat history from local database' and the specific tool description states '获取指定聊天的消息记录' (get messages from specified chat). The action is retrieval/querying with 'no side effects'.
Documented attack patterns abuse exactly the kind of access get_chat_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WeChat MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_chat_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_chat_history": {}
}
}get_chat_history 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.
获取指定聊天的消息记录。支持模糊匹配联系人名/备注名，支持按日期范围筛选。. It is categorised as a Read tool in the WeChat MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WeChat MCP Server MCP server in PolicyLayer and add a rule for get_chat_history: 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 WeChat MCP Server. Nothing to install.
get_chat_history 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 get_chat_history 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 get_chat_history. 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.
get_chat_history is provided by the WeChat MCP Server MCP server (sssssssynqa/wechat-claudecode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WeChat 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.
4 WeChat MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.