AI agents call search to retrieve information from MCP-DBLP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The search tool performs a read-only operation against the DBLP bibliography database. It retrieves publication records based on search criteria but does not create, modify, delete, or execute any code. The tool has minimal blast radius if misused by an AI agent, as it can only return bibliographic data already in the public DBLP database.
From the tool's definition Tool name is 'search' and description states 'Search DBLP for publications using a boolean query string' - this is a query operation that retrieves data from the DBLP database without modifying, deleting, or executing external operations.
Documented attack patterns abuse exactly the kind of access search 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 search:
{
"version": "1",
"default": "deny",
"tools": {
"search": {}
}
}search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search DBLP for publications using a boolean query string.\n. It is categorised as a Read tool in the MCP-DBLP MCP Server, which means it retrieves data without modifying state.
Register the MCP-DBLP MCP server in PolicyLayer and add a rule for search: 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.
search 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 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. 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 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.