project_number
The project's number. (number, required)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/project-number.md
What project_number does on GitHub
AI agents call project_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 project_number is rated Low
This tool simply retrieves or returns a project's identifying number. It is a read-only operation with no side effects, making it a Read category risk. The low severity reflects minimal potential for harm through misuse - exposing a project number does not directly endanger data, systems, or financial resources.
From the tool's definition Tool named 'project_number' is described as 'The project's number' - a field that retrieves or identifies a project identifier. No modification, deletion, execution, or financial operations are implied.
Attacks that exploit this kind of access
The rule that runs project_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 project_number, this is the rule to start with:
project_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 project_number call is checked against it from then on.
Questions about project_number
The project's number. (number, required). 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 project_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.
project_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 project_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 project_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.
project_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