Fetch a pull request with mergeability, reviewer, and diff summary details.
AI agents call get_pull_request to retrieve information from Universal Mcp Toolkit 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 query operation to fetch and display pull request information. It has no side effects, does not modify data, and does not execute code or commands. The blast radius of misuse is minimal—an agent could only access or enumerate pull request information, which is non-destructive information disclosure.
From the tool's definition Tool name 'get_pull_request' and description 'Fetch a pull request' indicate data retrieval. The tool retrieves pull request metadata (mergeability, reviewer, diff summary) without modifying or executing operations.
Attacks that exploit this kind of access
Fetch a pull request with mergeability, reviewer, and diff summary details. It is categorised as a Read tool in the Universal Mcp Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Universal Mcp Toolkit 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 Universal Mcp Toolkit. 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 Universal Mcp Toolkit MCP server (markgatcha/universal-mcp-toolkit). 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 →