List and filter repository pull requests
AI agents call list_pull_requests to retrieve information from Zerops Documentation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation—listing and filtering pull requests. It retrieves data from a repository with no side effects, modification, deletion, or execution of code. It is purely informational, making it a Read category tool with low severity.
From the tool's definition Tool name 'list_pull_requests' and description 'List and filter repository pull requests' indicate a query operation that retrieves and filters existing data without modification.
Attacks that exploit this kind of access
List and filter repository pull requests. It is categorised as a Read tool in the Zerops Documentation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zerops Documentation MCP Server 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 Zerops Documentation MCP Server. 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 Zerops Documentation MCP Server MCP server (nermalcat69/zerops-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 →