根据作者姓名搜索论文
AI agents call search_papers_by_author 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.
The tool retrieves or queries academic paper data based on an author parameter. It has no side effects—it only reads and returns search results from aggregated data sources (arXiv, Crossref, OpenAlex, PubMed, Semantic Scholar). No data is created, modified, deleted, or executed.
From the tool's definition Tool name is 'search_papers_by_author' and description indicates it searches papers by author name (根据作者姓名搜索论文 = 'search papers by author name').
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_by_author: 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_by_author 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_by_author 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_by_author. 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_by_author 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 →