Low Risk

githubSearchPullRequests

External PR archaeology: find when, why, and by whom code changed. Triage with type='metadata' first (no diff data), then re-call with type='fullContent' + prNumber for a specific PR's full diff, or type='partialContent' + partialContentMetadata for targeted file patches. Use current-source tools...

How to control githubSearchPullRequests ↓

What githubSearchPullRequests does on Octocode MCP - AI Context Platform

AI agents call githubSearchPullRequests to retrieve information from Octocode MCP - AI Context Platform without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
queries array Yes Array of queries for githubSearchPullRequests. Maximum is 5 queries per call. Multiple queries run in parallel. Use the per-query `page` field to navigate throu

Parameters from the server's own tool schema.

Low Risk

Why githubSearchPullRequests needs a policy

githubSearchPullRequests retrieves historical PR data and code changes from GitHub. Despite the detailed options (metadata, fullContent, partialContent), the tool only queries and extracts information; it does not create, modify, delete, or execute anything. The blast radius of misuse is limited to information disclosure (e.g., leaking sensitive diffs or PR metadata), which is a read-level risk.

From the tool's definition Tool performs PR archaeology and search operations—'find when, why, and by whom code changed'—with options to retrieve metadata, full diffs, or partial patches. All operations are read-only queries with no modify or delete capability.

Risk signalsAccepts freeform code/query input (queries[].query) · Accepts file system path (queries[].partialContentMetadata[].file) · High parameter count (46 properties)

Documented attack patterns abuse exactly the kind of access githubSearchPullRequests gives an agent:

How to control githubSearchPullRequests

PolicyLayer is an MCP gateway — it sits between your AI agents and Octocode MCP - AI Context Platform, and nothing reaches the server without passing your rules. This is the rule we recommend for githubSearchPullRequests:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "githubSearchPullRequests": {}
  }
}

githubSearchPullRequests is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Octocode MCP - AI Context Platform — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about githubSearchPullRequests

What does the githubSearchPullRequests tool do? +

External PR archaeology: find when, why, and by whom code changed. Triage with type='metadata' first (no diff data), then re-call with type='fullContent' + prNumber for a specific PR's full diff, or type='partialContent' + partialContentMetadata for targeted file patches. Use current-source tools to understand what code does now. It is categorised as a Read tool in the Octocode MCP - AI Context Platform MCP Server, which means it retrieves data without modifying state.

What parameters does githubSearchPullRequests accept? +

githubSearchPullRequests accepts 1 parameter: queries. Required: queries. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on githubSearchPullRequests? +

Register the Octocode MCP - AI Context Platform MCP server in PolicyLayer and add a rule for githubSearchPullRequests: 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 Octocode MCP - AI Context Platform. Nothing to install.

What risk level is githubSearchPullRequests? +

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

Can I rate-limit githubSearchPullRequests? +

Yes. Add a rate_limit block to the githubSearchPullRequests 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 githubSearchPullRequests completely? +

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

githubSearchPullRequests is provided by the Octocode MCP - AI Context Platform MCP server (octocode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Octocode MCP - AI Context Platform tool call.

Start from Octocode MCP - AI Context Platform, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

13 Octocode MCP - AI Context Platform tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.