Low Risk

get_recent_sessions

获取微信最近会话列表,包含最新消息摘要、未读数、时间等。

How to control get_recent_sessions ↓

What get_recent_sessions does on WeChat MCP Server

AI agents call get_recent_sessions 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.

Low Risk

Why get_recent_sessions needs a policy

This tool queries and retrieves session metadata from the local WeChat database without altering, deleting, or executing any operations. It is a pure data retrieval function with no side effects, fitting the Read category.

From the tool's definition Tool description states it retrieves (获取) WeChat recent sessions list with message summaries, unread counts, and timestamps. The server description emphasizes "read encrypted WeChat chat history" with actions limited to "read", "search", and "view".

Documented attack patterns abuse exactly the kind of access get_recent_sessions gives an agent:

How to control get_recent_sessions

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_recent_sessions:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_recent_sessions": {}
  }
}

get_recent_sessions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register WeChat MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_recent_sessions

What does the get_recent_sessions tool do? +

获取微信最近会话列表,包含最新消息摘要、未读数、时间等。. It is categorised as a Read tool in the WeChat MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_recent_sessions? +

Register the WeChat MCP Server MCP server in PolicyLayer and add a rule for get_recent_sessions: 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.

What risk level is get_recent_sessions? +

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

Can I rate-limit get_recent_sessions? +

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

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

get_recent_sessions 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.

Enforce policy on every WeChat MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.