Add a BibTeX entry to the collection for later export. Call this once for each paper you want to export.\n
AI agents use add_bibtex_entry 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 new BibTeX entries in a user's collection, which is a write operation. The modification is reversible (entries can be removed), and there is no destructive, executable, or financial component. The blast radius is minimal since it only affects the user's personal bibliography collection with no external side effects.
From the tool's definition Tool description states 'Add a BibTeX entry to the collection for later export', which is a create/add operation that modifies a collection reversibly.
Documented attack patterns abuse exactly the kind of access add_bibtex_entry 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 add_bibtex_entry:
{
"version": "1",
"default": "deny",
"tools": {
"add_bibtex_entry": {
"limits": [
{
"counter": "add_bibtex_entry_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_bibtex_entry 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.
Add a BibTeX entry to the collection for later export. Call this once for each paper you want to export.\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 add_bibtex_entry: 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.
add_bibtex_entry 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 add_bibtex_entry 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 add_bibtex_entry. 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.
add_bibtex_entry 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.