Export all collected BibTeX entries to a .bib file. Call this after adding all entries with add_bibtex_entry.\n
AI agents use export_bibtex to create or update resources in MCP-DBLP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-DBLP environment.
This tool creates and writes data to a .bib file, which is a reversible action typical of Write category tools. It does not execute arbitrary code, delete irreplaceable data, move money, or modify existing data destructively. The blast radius is minimal since BibTeX files are easily regenerated or deleted.
From the tool's definition Tool description states 'Export all collected BibTeX entries to a .bib file', indicating creation/writing of file data. The action is reversible—the exported file can be deleted or overwritten.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access export_bibtex gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-DBLP, and nothing reaches the server without passing your rules. This is the rule we recommend for export_bibtex:
{
"version": "1",
"default": "deny",
"tools": {
"export_bibtex": {
"limits": [
{
"counter": "export_bibtex_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_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.
Free to start. No card required.
Export all collected BibTeX entries to a .bib file. Call this after adding all entries with add_bibtex_entry.\n. It is categorised as a Write tool in the MCP-DBLP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-DBLP MCP server in PolicyLayer and add a rule for export_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 MCP-DBLP. Nothing to install.
export_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_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_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_bibtex is provided by the MCP-DBLP MCP server (szeider/mcp-dblp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 MCP-DBLP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 MCP-DBLP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.