AI agents invoke login_library to trigger actions in Library Access 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 initiates an authentication/login action against an external academic library system using configured credentials. It triggers an external operation (browser-based authentication session) whose effects depend on arguments and configuration. It is not a simple read — it establishes an authenticated session with side effects.
From the tool's definition 登录图书馆以获取学术资源访问权限。支持自动登录（需要配置凭据）或手动辅助。
Documented attack patterns abuse exactly the kind of access login_library gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Library Access MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for login_library:
{
"version": "1",
"default": "deny",
"tools": {
"login_library": {
"limits": [
{
"counter": "login_library_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}login_library 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 Library Access MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Library Access MCP server in PolicyLayer and add a rule for login_library: 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 Library Access MCP. Nothing to install.
login_library 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_library 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_library. 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_library is provided by the Library Access MCP server (yang-kun-long/library-access-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Library Access 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.
7 Library Access MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.