获取小红书登录二维码(扫码登录)
AI agents use xhs_login_qrcode to create or update resources in Xiaohongshu — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xiaohongshu environment.
An AI agent can call xhs_login_qrcode faster than any human can review — one bad instruction and it creates or modifies resources in Xiaohongshu by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
获取小红书登录二维码(扫码登录). It is categorised as a Write tool in the Xiaohongshu MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xiaohongshu MCP server in PolicyLayer and add a rule for xhs_login_qrcode: 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. Nothing to install.
xhs_login_qrcode 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 xhs_login_qrcode 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_login_qrcode. 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_login_qrcode is provided by the Xiaohongshu MCP server (lozzi1910/xiaohongshu-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 →