search_papers
AI agents call search_papers to retrieve information from Paper Distill MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool searches academic papers across multiple sources—a classic read operation that retrieves data without side effects. The empty description reduces confidence slightly, but the server's purpose (paper search and curation) and the pattern of sibling tools (collect for gathering, digest for summarizing) confirm this is a query/retrieval function. No data is modified, deleted, or financial impact occurs.
From the tool's definition Tool named 'search_papers' on an 'Academic paper search' server with sibling tools like 'collect', 'collect_to_zotero', and 'generate_digest' indicating retrieval and curation workflows rather than modification or execution.
Attacks that exploit this kind of access
search_papers. It is categorised as a Read tool in the Paper Distill MCP MCP Server, which means it retrieves data without modifying state.
Register the Paper Distill 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 Paper Distill MCP. 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 Paper Distill MCP server (pypi:paper-distill-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 →