AI agents use xhs_publish_content to create or update resources in Xhs — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xhs environment.
An AI agent can call xhs_publish_content faster than any human can review — one bad instruction and it creates or modifies resources in Xhs by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Publish content to XiaoHongShu (supports both images and videos). It is categorised as a Write tool in the Xhs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xhs MCP server in PolicyLayer and add a rule for xhs_publish_content: 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. Nothing to install.
xhs_publish_content 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 xhs_publish_content 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 xhs_publish_content. 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.
xhs_publish_content is provided by the Xhs MCP server (xhs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.