Retrieve multiple authors in a single request (max 1000).
AI agents call semantic_scholar_author_batch 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 performs a bulk read operation against the Semantic Scholar academic database. Retrieving author metadata produces no side effects, creates no obligations, and carries no destructive capability. The 'batch' functionality is a read optimization (1000 author limit). Misuse would be limited to information gathering, which poses minimal risk.
From the tool's definition Tool description states 'Retrieve multiple authors in a single request' — a pure retrieval operation with no data modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access semantic_scholar_author_batch 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 semantic_scholar_author_batch:
{
"version": "1",
"default": "deny",
"tools": {
"semantic_scholar_author_batch": {}
}
}semantic_scholar_author_batch 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.
Retrieve multiple authors in a single request (max 1000). 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 semantic_scholar_author_batch: 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.
semantic_scholar_author_batch 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 semantic_scholar_author_batch 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 semantic_scholar_author_batch. 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.
semantic_scholar_author_batch is provided by the Semantic Scholar MCP Server MCP server (smaniches/semantic-scholar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Semantic Scholar MCP Server, 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.
14 Semantic Scholar MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.