Search academic papers by keyword. Optional filters: year, venue.
AI agents call search_papers to retrieve information from Scholar Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries academic paper data without any side effects. It performs a search operation that returns metadata results but does not create, modify, delete, or execute any external operations.
From the tool's definition Tool description states 'Search academic papers by keyword' with optional filters for year and venue. The verb 'search' combined with the context of retrieving academic paper metadata indicates read-only functionality with no data modification or deletion.
Attacks that exploit this kind of access
Search academic papers by keyword. Optional filters: year, venue. It is categorised as a Read tool in the Scholar Search MCP Server, which means it retrieves data without modifying state.
Register the Scholar Search 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 Scholar Search. 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 Scholar Search MCP server (silung/scholar-search-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 →