Check review completion status for all your assigned papers.
AI agents call get_review_status to retrieve information from OpenReview MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the status of assigned papers' reviews. It performs no mutations, executions, or side effects—only retrieval of existing data. The blast radius of misuse is minimal: an attacker could learn which papers lack reviews, but cannot alter assignments, delete data, or trigger external actions. Categorized as Read with low severity.
From the tool's definition Tool description explicitly states 'Check review completion status' — a query operation that retrieves status information without modifying data. The name and description indicate read-only retrieval of review metadata.
Attacks that exploit this kind of access
Check review completion status for all your assigned papers. It is categorised as a Read tool in the OpenReview MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenReview MCP Server MCP server in PolicyLayer and add a rule for get_review_status: 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 MCP Server. Nothing to install.
get_review_status 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 get_review_status 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 get_review_status. 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.
get_review_status is provided by the OpenReview MCP Server MCP server (michaelqshieh/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 →