调用蓝奏云登录接口,并按响应头中是否存在 Set-Cookie 判断登录成功。
AI agents use lanzou_login to create or update resources in Lanzou MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lanzou MCP environment.
Authentication/login modifies the session state of an external service by establishing credentials and setting cookies. This is a Write operation rather than Read because it creates/modifies session state, though the effect is reversible.
From the tool's definition Tool performs authentication login to Lanzou Cloud service (蓝奏云登录接口 = 'Lanzou Cloud login interface'). Login operations modify session state by setting cookies (Set-Cookie), which is a reversible state change.
Attacks that exploit this kind of access
调用蓝奏云登录接口,并按响应头中是否存在 Set-Cookie 判断登录成功。. It is categorised as a Write tool in the Lanzou MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lanzou MCP server in PolicyLayer and add a rule for lanzou_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 Lanzou MCP. Nothing to install.
lanzou_login 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 lanzou_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 lanzou_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.
lanzou_login is provided by the Lanzou MCP server (k0itoyuu/lanzou-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 →