This record as markdown: /tools/io-github-iowarp-adios-mcp/search-by-abstract.md
What search_by_abstract does on CLIO Adios
AI agents call search_by_abstract 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_by_abstract is rated Low
This tool retrieves and queries data from ArXiv without side effects. The operation is read-only, searching for papers matching keyword criteria. The blast radius of misuse is minimal—worst case would be excessive requests or information disclosure of publicly available academic abstracts. No data is created, modified, deleted, or executed.
From the tool's definition Tool performs search operations on ArXiv papers by abstract keywords, with no modification, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
The rule that runs search_by_abstract 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_by_abstract, this is the rule to start with:
search_by_abstract 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_by_abstract call is checked against it from then on.
Questions about search_by_abstract
Search ArXiv papers by abstract keywords. 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_by_abstract: 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_by_abstract 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_by_abstract 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_by_abstract. 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_by_abstract 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