AI agents call list_pull_requests to retrieve information from Mcp Gmail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and filters pull request data from a GitHub repository. It performs a read-only query with no capability to modify, delete, or execute operations. The blast radius of misuse is minimal — an agent could at most retrieve sensitive PR information, but cannot alter repository state or trigger external actions.
From the tool's definition Tool name: 'list_pull_requests'; description: 'List pull requests in a GitHub repository with filtering options' — indicates a query/retrieval operation without side effects.
Attacks that exploit this kind of access
List pull requests in a GitHub repository with filtering options. It is categorised as a Read tool in the Mcp Gmail MCP Server, which means it retrieves data without modifying state.
Register the Mcp Gmail MCP server in PolicyLayer and add a rule for list_pull_requests: 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.
list_pull_requests 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 list_pull_requests 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 list_pull_requests. 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.
list_pull_requests 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 →