openreview_venue_stats

Compute submission count, acceptance rate, rating histogram, and decision breakdown for a venue (e.g. "ICLR.cc/2026/Conference").

Server Openreview opencodice-research/openreview-mcp
Category Read
Risk class Low
Parameters 00 required

What openreview_venue_stats does on Openreview

AI agents call openreview_venue_stats 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.

Why openreview_venue_stats needs a policy

This tool aggregates and computes statistics from existing submission and decision data. It has no side effects, does not modify data, does not execute code or commands, and does not delete or move data. It is a pure read operation that queries and returns analytical summaries of venue information, consistent with the 'Read' category for retrieval and queries with no side effects.

From the tool's definition The tool 'Compute submission count, acceptance rate, rating histogram, and decision breakdown' performs aggregation and statistical analysis of existing venue data without modifying, deleting, or executing external operations.

Questions about openreview_venue_stats

What does the openreview_venue_stats tool do? +

Compute submission count, acceptance rate, rating histogram, and decision breakdown for a venue (e.g. "ICLR.cc/2026/Conference"). It is categorised as a Read tool in the Openreview MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on openreview_venue_stats? +

Register the Openreview MCP server in PolicyLayer and add a rule for openreview_venue_stats: 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.

What risk level is openreview_venue_stats? +

openreview_venue_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit openreview_venue_stats? +

Yes. Add a rate_limit block to the openreview_venue_stats 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.

How do I block openreview_venue_stats completely? +

Set action: deny in the PolicyLayer policy for openreview_venue_stats. 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.

What MCP server provides openreview_venue_stats? +

openreview_venue_stats 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.