message_reviewer
AI agents use message_reviewer 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.
Based on the tool name and server context (conference reviewer workflows), this tool likely sends a message to a reviewer, which is a write/communication action. The description is empty, which lowers confidence. Given sibling tools like post_comment, this likely creates a new message, classified as Write. Severity is medium as misuse could send unwanted communications to reviewers.
From the tool's definition Tool name 'message_reviewer' and server context involving reviewer workflows; description is empty
Attacks that exploit this kind of access
message_reviewer. 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 message_reviewer: 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.
message_reviewer 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 message_reviewer 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 message_reviewer. 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.
message_reviewer 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 →