AI agents use request_reviewers to create or update resources in Mcp Gmail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Gmail environment.
This tool modifies pull request state by adding reviewers. It is not destructive (reviewers can be removed), does not execute arbitrary code, and has no financial impact. It is a reversible Write operation that changes PR metadata. Severity is medium because misuse could delay or redirect code reviews, but the impact is contained to review workflow and not data loss or system-level consequences.
From the tool's definition Tool performs 'request_reviewers for a pull request' — a modifying action that assigns reviewers to a pull request. This creates or updates pull request metadata reversibly.
Attacks that exploit this kind of access
Request reviewers for a pull request. It is categorised as a Write tool in the Mcp Gmail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Gmail MCP server in PolicyLayer and add a rule for request_reviewers: 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 Mcp Gmail. Nothing to install.
request_reviewers 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 request_reviewers 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 request_reviewers. 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.
request_reviewers is provided by the Mcp Gmail MCP server (@monsoft/mcp-gmail). 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 →