github_get_pull_request

Get a specific pull request

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}

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-alifanov-scopegate/github-get-pull-request.md

WHAT IT DOES

What github_get_pull_request does on ScopeGate

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

RISK

Why github_get_pull_request is rated Low

This tool retrieves information about a pull request, which is a read-only operation. It queries data without side effects—no resources are created, modified, deleted, or executed. The blast radius of misuse is minimal: an agent could retrieve PR information it shouldn't access, but cannot modify repositories, trigger workflows, or cause irreversible changes.

From the tool's definition Tool name 'github_get_pull_request' and description 'Get a specific pull request' indicate a retrieval operation with no modification, deletion, or code execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_get_pull_request safely

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

github_get_pull_request Allowed

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

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

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

FAQ

Questions about github_get_pull_request

What does the github_get_pull_request tool do? +

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

How do I enforce a policy on github_get_pull_request? +

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

What risk level is github_get_pull_request? +

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

Can I rate-limit github_get_pull_request? +

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

How do I block github_get_pull_request completely? +

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

What MCP server provides github_get_pull_request? +

github_get_pull_request is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScopeGate, and thousands of servers like it.

This server

All 385 ScopeGate tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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