new_name

New name for the label (used only with 'update' method to rename) (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/new-name.md

WHAT IT DOES

What new_name does on GitHub

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

RISK

Why new_name is rated Low

This appears to be a parameter definition rather than an actual tool. It describes a field ('new_name') used as input to a label-update operation, not a tool that performs an action on its own. Without a proper tool description, it cannot be meaningfully classified; however, if it were part of a label rename operation, it would be Write. Confidence is very low due to the uninformative description.

From the tool's definition Tool description says 'New name for the label (used only with update method to rename)' — this appears to be a parameter description, not a standalone tool description.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

new_name Rate-limited

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

FAQ

Questions about new_name

What does the new_name tool do? +

New name for the label (used only with 'update' method to rename) (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 new_name? +

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

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

Can I rate-limit new_name? +

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

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

new_name 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

new-fingerprint on AdsPower LocalAPI MCP Server → The MCP Attack Database →

Guides

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