discussionNumber
Discussion Number (number, required)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/discussionnumber.md
What discussionNumber does on GitHub
AI agents call discussionNumber 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 discussionNumber is rated Low
The tool appears to be a field or parameter used to identify and fetch discussion data by discussion number. This is a query/retrieval operation with no side effects. No data is modified, deleted, or executed. The severity is low because retrieving discussion metadata or content poses minimal risk even if misused.
From the tool's definition "Discussion Number (number, required)" - this is a parameter/identifier field that retrieves or references a specific discussion by its numeric ID, consistent with read operations in GitHub's discussion API.
Attacks that exploit this kind of access
The rule that runs discussionNumber 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 discussionNumber, this is the rule to start with:
discussionNumber 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 discussionNumber call is checked against it from then on.
Questions about discussionNumber
Discussion 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 discussionNumber: 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.
discussionNumber 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 discussionNumber 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 discussionNumber. 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.
discussionNumber 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