AI agents call xhs_get_queue_post_detail to retrieve information from XHS-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata and details about queued/scheduled posts for content creators. It performs a query operation with no side effects—it only reads information about posts awaiting publication. There is no modification, deletion, execution, or financial impact.
From the tool's definition Tool name contains 'get' and description states '根据文件名获取待发布笔记的详情' (get details of scheduled posts by filename, including title, content, images, tags). The verb 'get' and 'retrieve' operations are characteristic of Read operations.
Attacks that exploit this kind of access
根据文件名获取待发布笔记的详情（包括标题、内容、图片、标签等）. It is categorised as a Read tool in the XHS-MCP MCP Server, which means it retrieves data without modifying state.
Register the XHS- MCP server in PolicyLayer and add a rule for xhs_get_queue_post_detail: 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-MCP. Nothing to install.
xhs_get_queue_post_detail is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the xhs_get_queue_post_detail 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_get_queue_post_detail. 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_get_queue_post_detail is provided by the XHS- MCP server (lastkimi/xhs-mcp). 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 →