submit_meta_review
AI agents use submit_meta_review to create or update resources in OpenReview MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenReview MCP Server environment.
Meta-reviews are write actions that create new scholarly content and recommendations in a conference system. While reversible (reviews can be edited/modified via sibling 'edit_review' tool), they have significant consequences for paper acceptance decisions and author reputations.
From the tool's definition Tool name 'submit_meta_review' combined with sibling tools including 'confirm_submission' and 'edit_review' indicate this creates or modifies review content.
Attacks that exploit this kind of access
submit_meta_review. It is categorised as a Write tool in the OpenReview MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenReview MCP Server MCP server in PolicyLayer and add a rule for submit_meta_review: 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.
submit_meta_review is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the submit_meta_review 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 submit_meta_review. 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.
submit_meta_review 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 →