dblp.cs.author
Search 3M+ computer science authors on DBLP. Returns author name, DBLP PID, profile URL, aliases, affiliations. Use for finding researchers, checking publication records, or discovering collaborators (DBLP, CC0)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/dblp.cs.author.md
What dblp.cs.author does on Apibase
AI agents call dblp.cs.author to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Number of results (1-30, default 10) |
query | string | Yes | Author name to search (e.g. "Geoffrey Hinton", "Yann LeCun", "Ilya Sutskever") |
Parameters from the server's own tool schema.
Why dblp.cs.author is rated Low
Tool retrieves public researcher metadata from DBLP database without side effects.
From the tool's definition Search authors, returns name, PID, profile URL, aliases, affiliations. No modification.
Attacks that exploit this kind of access
The rule that runs dblp.cs.author safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dblp.cs.author, this is the rule to start with:
dblp.cs.author is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every dblp.cs.author call is checked against it from then on.
Questions about dblp.cs.author
Search 3M+ computer science authors on DBLP. Returns author name, DBLP PID, profile URL, aliases, affiliations. Use for finding researchers, checking publication records, or discovering collaborators (DBLP, CC0). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
dblp.cs.author accepts 2 parameters: limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for dblp.cs.author: 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 Apibase. Nothing to install.
dblp.cs.author 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 dblp.cs.author 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 dblp.cs.author. 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.
dblp.cs.author is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue