login_with_browser · Xhs Kit MCP: Risk & Policy

WHAT IT DOES

What login_with_browser does on Xhs Kit

AI agents invoke login_with_browser to trigger actions in Xhs Kit. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why login_with_browser needs a policy

This tool triggers an external browser automation action (opening a browser window for QR code scanning and authentication). It executes an external process with side effects including establishing a login session and likely storing cookies/credentials.

From the tool's definition 浏览器扫码登录（会弹出浏览器窗口）— 'will pop up a browser window', indicating it launches a browser process and performs an external login operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

login_with_browser Rate-limited

login_with_browser stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "login_with_browser": {
      "limits": [
        {
          "counter": "login_with_browser_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Xhs Kit, so you can run agents against it safely.

FAQ

Questions about login_with_browser

What does the login_with_browser tool do? +

浏览器扫码登录（会弹出浏览器窗口）。. It is categorised as a Execute tool in the Xhs Kit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on login_with_browser? +

Register the Xhs Kit MCP server in PolicyLayer and add a rule for login_with_browser: 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 Kit. Nothing to install.

What risk level is login_with_browser? +

login_with_browser is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit login_with_browser? +

Yes. Add a rate_limit block to the login_with_browser 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 login_with_browser completely? +

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

login_with_browser is provided by the Xhs Kit MCP server (luweizheng/xhs-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.