AI agents call list_venues 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 venue/conference metadata from academic paper collections. It performs a passive search query with no side effects, data modification, code execution, or destructive operations. The fuzzy search and counting are informational queries only. Misuse carries minimal risk as an AI agent cannot cause harm by browsing conference listings.
From the tool's definition Tool description states 'Search venues/conferences' with 'fuzzy' matching and 'per-collection counts'. All sibling tools (get_citation, get_collection, get_paper, list_authors, list_booktitles, list_collections, list_years, search_papers) are read-only…
Attacks that exploit this kind of access
Search venues/conferences (fuzzy). 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_venues: 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_venues 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_venues 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_venues. 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_venues 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 →