AI agents call list_authors to retrieve information from Verbatim without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists author information from an academic paper database. It performs a fuzzy search query and returns metadata (author names and collection counts) without creating, modifying, deleting, or executing any operations. This is a straightforward read-only query operation with minimal risk.
From the tool's definition Tool name is 'list_authors' and description states it 'Search[es] authors by name' and provides 'Per-collection counts'. These are pure retrieval operations with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
Search authors by name (fuzzy, typo-tolerant). Per-collection counts. It is categorised as a Read tool in the Verbatim MCP Server, which means it retrieves data without modifying state.
Register the Verbatim MCP server in PolicyLayer and add a rule for list_authors: 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 Verbatim. Nothing to install.
list_authors 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 list_authors 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 list_authors. 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.
list_authors is provided by the Verbatim MCP server (krlabsorg/verbatim-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →