Search submissions in a venue by title/abstract query, author name, or keywords.
AI agents call openreview_search_submissions 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 queries submission metadata (title, abstract, author, keywords) from OpenReview venues. It has no side effects—it only reads and returns data. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal (e.g., discovering submissions, identifying authors), making this a low-severity Read operation.
From the tool's definition Tool performs search and retrieval operations: 'Search submissions in a venue by title/abstract query, author name, or keywords.' It queries existing data without modifying, creating, deleting, or executing operations.
Attacks that exploit this kind of access
Search submissions in a venue by title/abstract query, author name, or keywords. 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_search_submissions: 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_search_submissions 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_search_submissions 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_search_submissions. 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_search_submissions 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 →