Search for papers on arXiv based on a topic and store their information.
AI agents call search_papers to retrieve information from 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 read operation that queries the arXiv database for academic papers based on search criteria. While it stores results locally, this is data retrieval with informational side effects only. There is no modification of arXiv data, no code execution triggered by user input, no data deletion, and no financial impact.
From the tool's definition Tool name and description: 'Search for papers on arXiv based on a topic and store their information.' The primary action is 'search' which retrieves and queries data from arXiv; 'store their information' refers to locally caching retrieved metadata, not…
Attacks that exploit this kind of access
Search for papers on arXiv based on a topic and store their information. It is categorised as a Read tool in the MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Server 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 MCP Server. 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 MCP Server MCP server (izzanzahrial/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 →