pull_request_number
The pull request number (use when item_type is 'pull_request' for 'add_project_item' method). Provide either issue_number or pull_request_number. (number, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/pull-request-number.md
What pull_request_number does on GitHub
AI agents call pull_request_number 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.
Why pull_request_number is rated Low
This tool serves as a query parameter or reference identifier used in read operations. It does not perform any side effects—it simply provides a numeric identifier to locate or retrieve pull request information. The context indicates it is used as input to identify which pull request to work with, making it a Read category tool with low severity.
From the tool's definition Tool description states 'The pull request number (use when item_type is 'pull_request' for 'add_project_item' method)' - this is a parameter/identifier for retrieving or referencing a pull request, not an action that modifies, executes, or deletes data.
Attacks that exploit this kind of access
The rule that runs pull_request_number 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_number, this is the rule to start with:
pull_request_number is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every pull_request_number call is checked against it from then on.
Questions about pull_request_number
The pull request number (use when item_type is 'pull_request' for 'add_project_item' method). Provide either issue_number or pull_request_number. (number, optional). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP server in PolicyLayer and add a rule for pull_request_number: 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.
pull_request_number 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 pull_request_number 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 pull_request_number. 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.
pull_request_number 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.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue