confirm_submission · OpenReview MCP Server MCP

WHAT IT DOES

What confirm_submission does on OpenReview MCP Server

AI agents use confirm_submission 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.

WHY IT NEEDS A POLICY

Why confirm_submission needs a policy

This tool finalizes and publishes a review, meta-review, or comment to OpenReview. While it is a write/publish action (not destructive or financial), the severity is high because submitting an official review or meta-review in an academic conference context can have significant real-world consequences for authors and the review process.

From the tool's definition Confirm and submit a pending review, meta-review, or comment to OpenReview

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

confirm_submission Rate-limited

confirm_submission stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "confirm_submission": {
      "limits": [
        {
          "counter": "confirm_submission_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches OpenReview MCP Server, so you can run agents against it safely.

FAQ

Questions about confirm_submission

What does the confirm_submission tool do? +

Confirm and submit a pending review, meta-review, or comment to OpenReview. 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.

How do I enforce a policy on confirm_submission? +

Register the OpenReview MCP Server MCP server in PolicyLayer and add a rule for confirm_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.

What risk level is confirm_submission? +

confirm_submission is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit confirm_submission? +

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

How do I block confirm_submission completely? +

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

What MCP server provides confirm_submission? +

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