AI agents use reply_comment to create or update resources in Xhs Kit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xhs Kit environment.
This tool creates or adds new data (a comment reply) to existing content, which is a reversible Write operation. It does not execute arbitrary code, delete data, or move money. The severity is medium because misuse could result in spam, harassment, or unwanted replies posted to the platform, but the effects are reversible and limited to comment creation.
From the tool's definition Tool name 'reply_comment' and description '回复笔记下的指定评论' (reply to a specified comment under a note) indicate the tool creates new content (a reply/comment) on the Xiaohongshu platform.
Attacks that exploit this kind of access
回复笔记下的指定评论. It is categorised as a Write tool in the Xhs Kit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xhs Kit MCP server in PolicyLayer and add a rule for reply_comment: 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 Xhs Kit. Nothing to install.
reply_comment 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 reply_comment 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 reply_comment. 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.
reply_comment is provided by the Xhs Kit MCP server (luweizheng/xhs-kit). 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 →