AI agents call xhs_user_profile 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 retrieves user profile information from Xiaohongshu without any capability to modify, delete, or execute operations. It is a simple data fetch operation consistent with Read category. The read-only nature of the entire server and the passive verb 'Get' confirm this classification. Severity is low as unauthorized access to public user profiles has minimal impact.
From the tool's definition Tool name 'xhs_user_profile' and description 'Get a Xiaohongshu user' indicate data retrieval. Server description explicitly states 'read-only access' and lists 'user profiles' as a capability.
Attacks that exploit this kind of access
Get a Xiaohongshu user. 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_user_profile: 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_user_profile 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_user_profile 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_user_profile. 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_user_profile 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 →