search_pull_requests

A read tool on the GitHub MCP server.

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/search-pull-requests.md

WHAT IT DOES

What search_pull_requests does on GitHub

AI agents call search_pull_requests 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 search_pull_requests is rated Low

This is a read-only operation that searches and retrieves pull request information from GitHub. It has no side effects, does not execute code, does not modify data, and does not delete anything. The search functionality is characteristic of Read category tools.

From the tool's definition Tool name 'search_pull_requests' and description 'Search pull requests' indicate a query operation that retrieves existing pull request data without modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_pull_requests 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 search_pull_requests, this is the rule to start with:

search_pull_requests Allowed

search_pull_requests 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": {
    "search_pull_requests": {}
  }
}

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 search_pull_requests call is checked against it from then on.

FAQ

Questions about search_pull_requests

What does the search_pull_requests tool do? +

search_pull_requests is a read tool on the GitHub MCP server. 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 search_pull_requests? +

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

What risk level is search_pull_requests? +

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

Can I rate-limit search_pull_requests? +

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

How do I block search_pull_requests completely? +

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

What MCP server provides search_pull_requests? +

search_pull_requests 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

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

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