AI agents use publish_with_video 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 and publishes new content (video posts) on Xiaohongshu, which is a reversible modification operation. While the content is posted publicly, the action itself can be undone by deleting the post. This fits the Write category rather than Execute because it is a content creation operation with predictable effects, not arbitrary code execution.
From the tool's definition Tool name 'publish_with_video' and description '发布小红书视频内容(仅支持本地单个视频文件)' (Publish Xiaohongshu video content - supports only local single video files) indicates content creation and posting to a social media 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 publish_with_video: 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.
publish_with_video 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 publish_with_video 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 publish_with_video. 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.
publish_with_video 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 →