side

The side of the diff to comment on. LEFT indicates the previous state, RIGHT indicates the new state (string, 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/side.md

WHAT IT DOES

What side does on GitHub

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

RISK

Why side is rated Low

This appears to be a parameter descriptor rather than an actual MCP tool. It describes an optional string parameter used to specify the side of a diff for commenting purposes. It has no independent action or side effect on its own. Confidence is low due to the uninformative/misleading tool definition.

From the tool's definition The description 'The side of the diff to comment on. LEFT indicates the previous state, RIGHT indicates the new state (string, optional)' describes a parameter, not a standalone tool.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

side Rate-limited

side 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": {
    "side": {
      "limits": [
        {
          "counter": "side_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 side call is checked against it from then on.

FAQ

Questions about side

What does the side tool do? +

The side of the diff to comment on. LEFT indicates the previous state, RIGHT indicates the new state (string, 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 side? +

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

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

Can I rate-limit side? +

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

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

side 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 →