pull_request_read

Get details for a single pull request

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/pull-request-read.md

WHAT IT DOES

What pull_request_read does on GitHub

AI agents call pull_request_read to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why pull_request_read is rated Low

This tool retrieves metadata and content from an existing pull request without creating, modifying, deleting, or executing any actions. It is a standard query operation with minimal security risk.

From the tool's definition Tool name includes 'read' and description states 'Get details for a single pull request' — a pure retrieval operation with no side effects or modifications.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pull_request_read safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pull_request_read, this is the rule to start with:

pull_request_read Allowed

pull_request_read is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pull_request_read": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every pull_request_read call is checked against it from then on.

FAQ

Questions about pull_request_read

What does the pull_request_read tool do? +

Get details for a single pull request. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pull_request_read? +

Register the GitHub MCP server in PolicyLayer and add a rule for pull_request_read: 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 GitHub. Nothing to install.

What risk level is pull_request_read? +

pull_request_read is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pull_request_read? +

Yes. Add a rate_limit block to the pull_request_read 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.

How do I block pull_request_read completely? +

Set action: deny in the PolicyLayer policy for pull_request_read. 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.

What MCP server provides pull_request_read? +

pull_request_read is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →