AI agents call author_papers to retrieve information from Semantic Scholar MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves academic paper metadata for a given author. No description is provided, lowering confidence slightly, but the naming pattern and context of sibling tools (all queries/reads) strongly indicate a read-only retrieval operation with no side effects, data modification, or external execution. The Semantic Scholar API is a public academic database access service.
From the tool's definition Tool name 'author_papers' with empty description; sibling tools on this server include 'author_details', 'author_search', 'paper_authors', 'paper_citations', and 'paper_batch_details'—all retrieval/query operations.
Documented attack patterns abuse exactly the kind of access author_papers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Semantic Scholar MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for author_papers:
{
"version": "1",
"default": "deny",
"tools": {
"author_papers": {}
}
}author_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.
author_papers. It is categorised as a Read tool in the Semantic Scholar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Semantic Scholar MCP Server MCP server in PolicyLayer and add a rule for author_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 Semantic Scholar MCP Server. Nothing to install.
author_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 author_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 author_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.
author_papers is provided by the Semantic Scholar MCP Server MCP server (zongmin-yu/semantic-scholar-fastmcp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Semantic Scholar MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Semantic Scholar MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.