search_date_range
Search ArXiv papers within a specific date range.
This record as markdown: /tools/io-github-iowarp-adios-mcp/search-date-range.md
What search_date_range does on CLIO Adios
AI agents call search_date_range to retrieve information from CLIO Adios without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_date_range is rated Low
This tool queries ArXiv for papers matching date criteria, returning search results. It retrieves data without modifying, deleting, executing code, or committing financial actions. The operation is read-only and has minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'search_date_range' and description 'Search ArXiv papers within a specific date range' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs search_date_range safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CLIO Adios, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_date_range, this is the rule to start with:
search_date_range is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CLIO Adios, apply this rule, and every search_date_range call is checked against it from then on.
Questions about search_date_range
Search ArXiv papers within a specific date range. It is categorised as a Read tool in the CLIO Adios MCP Server, which means it retrieves data without modifying state.
Register the CLIO Adios MCP server in PolicyLayer and add a rule for search_date_range: 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 CLIO Adios. Nothing to install.
search_date_range 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_date_range 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_date_range. 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_date_range is provided by the CLIO Adios MCP server (pypi:clio-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CLIO Adios, and thousands of servers like it.
This server
Across the catalogue