get_submission
AI agents call get_submission 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.
The tool retrieves submission information as part of OpenReview's conference management workflow. This is a standard read operation—querying paper submissions—with no side effects. No data is modified, deleted, or executed. The empty description prevents full certainty, but the tool name and server purpose strongly indicate this is a straightforward read operation appropriate for reviewer workflows.
From the tool's definition Tool name 'get_submission' indicates retrieval of submission data. Server description states it 'enables users to manage paper assignments, read submissions and reviews' and characterizes submission reading as part of core reviewer workflows.
Attacks that exploit this kind of access
get_submission. 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_submission: 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_submission 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_submission 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_submission. 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_submission 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 →