AI agents use wechat_send_to_multiple_friends to create or update resources in Wechat — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wechat environment.
The tool sends messages to multiple WeChat friends, which creates new data (messages) but is reversible through deletion or editing. While it affects multiple recipients and could be misused for spam or unauthorized communication at scale, it is not Financial (no money involved), not Destructive (messages can be deleted), and not Execute (no arbitrary code execution).
From the tool's definition Tool description states '向多个微信好友发送单条或者多条消息' (send single or multiple messages to multiple WeChat friends). This is a Write operation that creates/sends messages to multiple recipients.
Attacks that exploit this kind of access
向多个微信好友发送单条或者多条消息. It is categorised as a Write tool in the Wechat MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wechat MCP server in PolicyLayer and add a rule for wechat_send_to_multiple_friends: 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. Nothing to install.
wechat_send_to_multiple_friends is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wechat_send_to_multiple_friends 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 wechat_send_to_multiple_friends. 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.
wechat_send_to_multiple_friends is provided by the Wechat MCP server (panxingfeng/mcp_server_wechat). 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 →