AI agents call xhs_note_detail to retrieve information from Xhs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a data retrieval operation with no side effects. It queries and returns information about a note but does not create, modify, delete, or execute any actions.
From the tool's definition Tool description states it 'Get[s] full detail of a specific Xiaohongshu note by ID' and 'Returns the complete content, all images, engagement metrics, author info, and tags.' No modification, deletion, or execution capability is mentioned.
Attacks that exploit this kind of access
Get full detail of a specific Xiaohongshu note by ID. Returns the complete content, all images, engagement metrics, author info, and tags. Use note IDs from xhs_search results. It is categorised as a Read tool in the Xhs MCP Server, which means it retrieves data without modifying state.
Register the Xhs MCP server in PolicyLayer and add a rule for xhs_note_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. Nothing to install.
xhs_note_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_note_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_note_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_note_detail is provided by the Xhs MCP server (xyj2570/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 →