Fetch an OpenReview user profile by id (e.g. "~First_Last1") or email.
AI agents call openreview_get_profile 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 performs a simple data retrieval operation on user profile information from OpenReview. It has no side effects, does not modify any data, and does not execute code or commands. The action is informational only and consistent with Read category tools like 'get' and 'fetch'.
From the tool's definition Tool name 'openreview_get_profile' and description 'Fetch an OpenReview user profile by id or email' indicate retrieval of publicly available profile data with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Fetch an OpenReview user profile by id (e.g. "~First_Last1") or email. 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_profile: 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_profile 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_profile 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_profile. 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_profile 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 →