before_id

The ID of the sub-issue to be prioritized before (either after_id OR before_id should be specified) (number, optional)

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/before-id.md

WHAT IT DOES

What before_id does on GitHub

AI agents call before_id as a supporting operation in GitHub workflows.

RISK

Why before_id is rated Low

This does not appear to be an actionable tool but rather a parameter definition for ordering sub-issues. It describes an input field (before_id) used in conjunction with after_id for prioritization. As a parameter rather than an executable tool, it cannot be meaningfully classified into an action category.

From the tool's definition The tool description reads: 'The ID of the sub-issue to be prioritized before (either after_id OR before_id should be specified) (number, optional)' — this appears to be a parameter descriptor, not a standalone tool.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs before_id 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 before_id, this is the rule to start with:

before_id Rate-limited

before_id gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "before_id": {
      "limits": [
        {
          "counter": "before_id_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about before_id

What does the before_id tool do? +

The ID of the sub-issue to be prioritized before (either after_id OR before_id should be specified) (number, optional). It is categorised as a Other tool in the GitHub MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on before_id? +

Register the GitHub MCP server in PolicyLayer and add a rule for before_id: 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.

What risk level is before_id? +

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

Can I rate-limit before_id? +

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

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

before_id 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.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →