AI agents call search_papers to retrieve information from Library Access MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information from academic databases without creating, modifying, or deleting data. It has no side effects beyond returning search results. While it accesses authenticated academic databases, the search operation itself is read-only. The low severity reflects minimal blast radius—misuse would return irrelevant results but cause no data loss, financial impact, or system compromise.
From the tool's definition Tool name 'search_papers' and description indicate a search function in academic databases. The description '在学术数据库中搜索论文' translates to 'search papers in academic databases', which is a retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access search_papers 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 search_papers:
{
"version": "1",
"default": "deny",
"tools": {
"search_papers": {}
}
}search_papers is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
在学术数据库中搜索论文. It is categorised as a Read tool in the Library Access MCP MCP Server, which means it retrieves data without modifying state.
Register the Library Access MCP server in PolicyLayer and add a rule for search_papers: 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.
search_papers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_papers 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 search_papers. 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.
search_papers 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.