List OpenReview venues, optionally filtered by year (e.g. 2026) or series substring (e.g. "ICLR").
AI agents call openreview_list_venues to retrieve information from Openreview without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and optionally filters a list of existing OpenReview venues. It performs no side effects, creates no data, executes no code, and modifies nothing. It is a straightforward read operation with minimal blast radius—misuse would at worst allow an agent to enumerate venues, which is non-sensitive metadata already public on OpenReview.
From the tool's definition Tool name 'openreview_list_venues' and description 'List OpenReview venues' indicate retrieval/enumeration of venue metadata. The description contains only read verbs: 'List', with optional filtering parameters.
Attacks that exploit this kind of access
List OpenReview venues, optionally filtered by year (e.g. 2026) or series substring (e.g. "ICLR"). It is categorised as a Read tool in the Openreview MCP Server, which means it retrieves data without modifying state.
Register the Openreview MCP server in PolicyLayer and add a rule for openreview_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 Openreview. Nothing to install.
openreview_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 openreview_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 openreview_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.
openreview_list_venues is provided by the Openreview MCP server (opencodice-research/openreview-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 →