Search for scientific papers based on a query using Semantic Scholar API.
AI agents call search_papers to retrieve information from Basic MCP Application without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from an external API (Semantic Scholar) based on user input. It has no side effects, does not modify or delete data, and does not execute arbitrary code or trigger external operations beyond a standard search query. The primary function is read-only data retrieval, making it a Read category risk with low severity.
From the tool's definition Tool name 'search_papers' and description explicitly states it 'Search for scientific papers based on a query using Semantic Scholar API' — a query operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Search for scientific papers based on a query using Semantic Scholar API. It is categorised as a Read tool in the Basic MCP Application MCP Server, which means it retrieves data without modifying state.
Register the Basic MCP Application 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 Basic MCP Application. 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 Basic MCP Application MCP server (priteshshah96/mcp). 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 →