在多个学术数据库中搜索论文，支持学科智能选择数据源
AI agents call search_papers to retrieve information from Academic Paper MCP HTTP/SSE Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward search operation across academic literature databases (arXiv, Crossref, OpenAlex, PubMed, Semantic Scholar). It retrieves information only—no data modification, deletion, code execution, or financial transactions are possible. Misuse would yield unwanted search results at worst, posing minimal risk. Classified as Read with low severity.
From the tool's definition Tool name is 'search_papers' and description indicates it 'searches papers in multiple academic databases' with intelligent source selection. No mention of modification, deletion, execution, or financial operations.
Attacks that exploit this kind of access
在多个学术数据库中搜索论文，支持学科智能选择数据源. It is categorised as a Read tool in the Academic Paper MCP HTTP/SSE Server MCP Server, which means it retrieves data without modifying state.
Register the Academic Paper MCP HTTP/SSE Server 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 Academic Paper MCP HTTP/SSE Server. 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 Academic Paper MCP HTTP/SSE Server MCP server (pastchais/academic-paper-mcp-http). 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 →