AI agents call search_openreview to retrieve information from Scholar without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves academic papers or metadata from OpenReview, a common open-access paper repository. No description is provided, which slightly lowers confidence, but the naming pattern and server context (research/search focused) strongly suggest this is a data retrieval tool with no side effects. It fits the 'Read' category as it queries and retrieves information without creating, modifying, or deleting data.
From the tool's definition Tool name 'search_openreview' indicates querying an academic paper repository (OpenReview); sibling tools include 'search_papers', 'search_authors', 'read_paper', and 'recommend_papers' which are all read operations.
Attacks that exploit this kind of access
search_openreview. It is categorised as a Read tool in the Scholar MCP Server, which means it retrieves data without modifying state.
Register the Scholar MCP server in PolicyLayer and add a rule for search_openreview: 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 Scholar. Nothing to install.
search_openreview 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 search_openreview 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 search_openreview. 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.
search_openreview is provided by the Scholar MCP server (liyux3/scholar-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 →