Search for academic papers.
AI agents call semantic_scholar_search_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 is a search tool that retrieves academic paper metadata from Semantic Scholar's 200M+ paper database. It performs information lookup without side effects—no creation, modification, deletion, code execution, or financial operations. Even if an AI agent misuses it by searching excessively, the worst outcome is API rate-limiting or resource consumption, not data corruption or unauthorized actions.
From the tool's definition Tool name 'semantic_scholar_search_papers' and description 'Search for academic papers' indicate a query/retrieval operation with no data modification or execution capability.
Documented attack patterns abuse exactly the kind of access semantic_scholar_search_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 semantic_scholar_search_papers:
{
"version": "1",
"default": "deny",
"tools": {
"semantic_scholar_search_papers": {}
}
}semantic_scholar_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.
Search for academic 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 semantic_scholar_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 Semantic Scholar MCP Server. Nothing to install.
semantic_scholar_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 semantic_scholar_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 semantic_scholar_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.
semantic_scholar_search_papers 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.