Fetch full metadata for a submission by its forum/note id.
AI agents call openreview_get_submission 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 submission metadata from OpenReview without any side effects or modifications. It is a straightforward data query operation, similar to the sibling tools like 'openreview_get_profile', 'openreview_get_reviews', and 'openreview_search_submissions', all of which are read operations.
From the tool's definition Tool name 'openreview_get_submission' and description 'Fetch full metadata for a submission' indicate data retrieval with no modification. The verb 'Fetch' and absence of any create/update/delete/execute language confirms read-only operation.
Attacks that exploit this kind of access
Fetch full metadata for a submission by its forum/note id. 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_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. Nothing to install.
openreview_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 openreview_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 openreview_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.
openreview_get_submission 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 →