Search DBLP for publications with fuzzy title matching.\n
AI agents call fuzzy_title_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.
This tool performs a fuzzy search against the DBLP bibliography database to find publications matching a title pattern. It retrieves information only and has no side effects. The action is purely informational lookup, consistent with the Read category (search, query, fetch operations). No data is created, modified, deleted, or destroyed; no code is executed; and no financial operations occur.
From the tool's definition Tool name and description indicate 'Search DBLP for publications with fuzzy title matching' — a query operation that retrieves data without modifying or executing code.
Documented attack patterns abuse exactly the kind of access fuzzy_title_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 fuzzy_title_search:
{
"version": "1",
"default": "deny",
"tools": {
"fuzzy_title_search": {}
}
}fuzzy_title_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 with fuzzy title matching.\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 fuzzy_title_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.
fuzzy_title_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 fuzzy_title_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 fuzzy_title_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.
fuzzy_title_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.