Get detailed information about a specific pull request.
AI agents call get_pull_request 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 performs a straightforward data retrieval operation. It fetches and returns information about an existing pull request without creating, modifying, deleting, or executing any operations. It is analogous to a GET request in REST semantics, making it a clear Read category tool with low severity.
From the tool's definition get_pull_request retrieves detailed information about a specific pull request. The verb 'get' and the read-only nature of querying pull request metadata indicate no data modification or side effects.
Attacks that exploit this kind of access
Get detailed information about a specific pull request. 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 get_pull_request: 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.
get_pull_request 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 get_pull_request 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 get_pull_request. 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.
get_pull_request 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.
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 →