AI agents invoke login to trigger actions in FishClaw MCP. 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.
This tool does more than just read data; it executes a browser automation action (launching/controlling a browser to display a QR code for login). It falls under Execute because it triggers an external operation (browser interaction) whose effects depend on the current login state. Severity is medium because misuse could initiate unauthorized login sessions or interfere with the user's browser session.
From the tool's definition 打开浏览器展示二维码 — the tool triggers a browser automation action (opening a browser and displaying a QR code) via Playwright
Documented attack patterns abuse exactly the kind of access login gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and FishClaw MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for login:
{
"version": "1",
"default": "deny",
"tools": {
"login": {
"limits": [
{
"counter": "login_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}login 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.
Free to start. No card required.
检查闲鱼登录状态。已登录则直接返回；未登录则打开浏览器展示二维码，. It is categorised as a Execute tool in the FishClaw MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the FishClaw MCP server in PolicyLayer and add a rule for login: 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 FishClaw MCP. Nothing to install.
login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the login 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 login. 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.
login is provided by the FishClaw MCP server (tnoobt/fishclaw_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from FishClaw MCP, 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.
12 FishClaw MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.