color

Label color as 6-character hex code without '#' prefix (e.g., 'f29513'). Required for 'create', optional for 'update'. (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/color.md

WHAT IT DOES

What color does on GitHub

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

RISK

Why color is rated Low

This appears to be a parameter/property descriptor for a label color value rather than a standalone tool. It describes a color input field used when creating or updating GitHub labels. As a parameter rather than an action, it doesn't independently perform any operation. Classifying as Other with low confidence since the description is not that of an executable tool but rather a field specification.

From the tool's definition 'Label color as 6-character hex code without '#' prefix (e.g., 'f29513'). Required for 'create', optional for 'update'.'

Attacks that exploit this kind of access

RECOMMENDED RULE

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

color Rate-limited

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

FAQ

Questions about color

What does the color tool do? +

Label color as 6-character hex code without '#' prefix (e.g., 'f29513'). Required for 'create', optional for 'update'. (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 color? +

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

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

Can I rate-limit color? +

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

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

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