export_to_bibtex
Export search results to BibTeX format for citation management.
This record as markdown: /tools/io-github-iowarp-adios-mcp/export-to-bibtex.md
What export_to_bibtex does on CLIO Adios
AI agents use export_to_bibtex to create or update resources in CLIO Adios, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CLIO Adios environment.
Why export_to_bibtex is rated Medium
This tool creates new data (BibTeX-formatted citation files) from existing search results. It is reversible and has no side effects on the original data source. It does not execute arbitrary code, delete data, or move money. The blast radius of misuse is minimal—a user could generate unwanted citation files, but these are trivial to remove and pose no risk to underlying data integrity or system security.
From the tool's definition Tool description states 'Export search results to BibTeX format for citation management.' The verb 'export' and action of writing results to a new format indicate data creation/modification.
Attacks that exploit this kind of access
The rule that runs export_to_bibtex 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 export_to_bibtex, this is the rule to start with:
export_to_bibtex stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 export_to_bibtex call is checked against it from then on.
Questions about export_to_bibtex
Export search results to BibTeX format for citation management. It is categorised as a Write tool in the CLIO Adios MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CLIO Adios MCP server in PolicyLayer and add a rule for export_to_bibtex: 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.
export_to_bibtex is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the export_to_bibtex 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 export_to_bibtex. 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.
export_to_bibtex 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