Low Risk

get_xhs_user_info

通过用户 ID 获取小红书用户的信息。

How to control get_xhs_user_info ↓

What get_xhs_user_info does on Xiaohongshu API MCP Server

AI agents call get_xhs_user_info to retrieve information from Xiaohongshu API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_xhs_user_info needs a policy

This tool retrieves and returns user profile information without modifying, deleting, or executing any operations. It is a straightforward read operation similar to other data retrieval tools on the server (get_xhs_feed, get_xhs_note, search_xhs_users). The blast radius of misuse is minimal—an agent could retrieve unwanted user data but cannot create, modify, or delete information.

From the tool's definition Tool name 'get_xhs_user_info' and description indicate retrieval of user information by ID. The description states '通过用户 ID 获取小红书用户的信息' (Get Xiaohongshu user information through user ID), which is a query/fetch operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_xhs_user_info gives an agent:

How to control get_xhs_user_info

PolicyLayer is an MCP gateway — it sits between your AI agents and Xiaohongshu API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_xhs_user_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_xhs_user_info": {}
  }
}

get_xhs_user_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Xiaohongshu API MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_xhs_user_info

What does the get_xhs_user_info tool do? +

通过用户 ID 获取小红书用户的信息。. It is categorised as a Read tool in the Xiaohongshu API MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_xhs_user_info? +

Register the Xiaohongshu API MCP Server MCP server in PolicyLayer and add a rule for get_xhs_user_info: 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 Xiaohongshu API MCP Server. Nothing to install.

What risk level is get_xhs_user_info? +

get_xhs_user_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_xhs_user_info? +

Yes. Add a rate_limit block to the get_xhs_user_info 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.

How do I block get_xhs_user_info completely? +

Set action: deny in the PolicyLayer policy for get_xhs_user_info. 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.

What MCP server provides get_xhs_user_info? +

get_xhs_user_info is provided by the Xiaohongshu API MCP Server MCP server (proerror77/xhs_mcp_agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Xiaohongshu API MCP Server tool call.

Start from Xiaohongshu API MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

9 Xiaohongshu API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.