list_pull_requests
AI agents call list_pull_requests to retrieve information from Mcp Pagure without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or enumerates pull requests without altering state. Though the description is empty, the name and context clearly indicate read-only functionality. The blast radius of misuse is minimal—listing PRs exposes information but cannot cause damage.
From the tool's definition Tool name 'list_pull_requests' indicates retrieval of pull request data with no modification. Sibling tools show a pattern where read operations (get_commit, get_file, get_project_info, get_pull_request, list_branches, list_projects) are distinct from…
Attacks that exploit this kind of access
list_pull_requests. It is categorised as a Read tool in the Mcp Pagure MCP Server, which means it retrieves data without modifying state.
Register the Mcp Pagure 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 Pagure. 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 Pagure MCP server (lemenkov/mcp-pagure). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
list_pull_requests is one line of Mcp Pagure's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →