// SCAN REPORT

Library Access MCP

7 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated: 12 Jun 2026

3 can modify or destroy data

4 read-only

7 tools total

Community server · catalogue entry verified 12/06/2026

How to control Library Access MCP ↓

TOOL MAP

What Library Access MCP exposes to your agents

Read (4) Write / Execute (3) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Library Access MCP tools

Execute · High login_library This tool initiates an authentication/login action against an external academic library system using configured credentials. Execute · High open_url This tool triggers a browser action to navigate to an arbitrary URL. Write · Medium persist_paper This tool writes paper metadata to the local filesystem under a Research/ directory.

3 of Library Access MCP's 7 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Library Access MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Library Access MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "persist_paper": {
    "limits": [
      {
        "counter": "persist_paper_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "download_paper": {
    "limits": [
      {
        "counter": "download_paper_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Library Access MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON LIBRARY ACCESS →

Free to start. No card required.

FULL CATALOGUE

All 7 Library Access MCP tools

EXECUTE 2 tools

Execute login_library 登录图书馆以获取学术资源访问权限。支持自动登录（需要配置凭据）或手动辅助。 Execute open_url 在浏览器中打开指定 URL

WRITE 1 tools

Write persist_paper 将抓取的论文元数据固化到本地 Research/ 目录

READ 4 tools

Read download_paper 在浏览器中打开论文获取途径页面，供用户自行下载。建议使用 get_paper_detail 返回的 accessLinks 中的 URL。 Read get_paper_detail 获取论文详情页的完整摘要、作者、关键词、DOI、期刊名等信息 Read ping_test 测试与浏览器插件的连接 Read search_papers 在学术数据库中搜索论文

FAQ

Questions about Library Access MCP

How do I prevent bulk modifications through Library Access MCP? +

The Library Access MCP server has 1 write tools including persist_paper. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Library Access MCP.

How many tools does the Library Access MCP server expose? +

7 tools across 2 categories: Read, Write. 4 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Library Access MCP? +

Register the Library Access MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Library Access MCP tool call.

Deterministic rules across all 7 Library Access MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON LIBRARY ACCESS →

Free to start. No card required.

7 Library Access MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.