after_id

The ID of the sub-issue to be prioritized after (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 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-aifity-omnigit-mcp/after-id.md

WHAT IT DOES

What after_id does on GitHub

AI agents call after_id 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.

RISK

Why after_id is rated Low

This appears to be a parameter for sorting or filtering sub-issues by ID rather than an action tool itself. The description indicates it is used to retrieve or order data (specifying position relative to another issue ID) without modifying state.

From the tool's definition Tool parameter description states it specifies 'The ID of the sub-issue to be prioritized after' with no indication of modification or deletion. Named 'after_id' suggesting it queries or filters issue ordering.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

after_id Allowed

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

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

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

FAQ

Questions about after_id

What does the after_id tool do? +

The ID of the sub-issue to be prioritized after (either after_id OR before_id should be specified) (number, optional). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on after_id? +

Register the GitHub MCP server in PolicyLayer and add a rule for after_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 after_id? +

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

Can I rate-limit after_id? +

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

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

after_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 →Data exfiltration →MCP token cost →