state_reason

Reason for the state change. Ignored unless state is changed. (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/state-reason.md

WHAT IT DOES

What state_reason does on GitHub

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

RISK

Why state_reason is rated Low

The description reads like a parameter definition (a string field for providing a reason when changing state), not an independent tool that performs an action. It has no clear side effect on its own. Confidence is low because the description is uninformative as a tool description, making classification uncertain. Categorized as Other since it doesn't independently read, write, execute, destroy, or move money.

From the tool's definition Tool description: 'Reason for the state change. Ignored unless state is changed. (string, optional)' — this appears to be a parameter descriptor, not a standalone tool with its own action.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

state_reason Rate-limited

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

FAQ

Questions about state_reason

What does the state_reason tool do? +

Reason for the state change. Ignored unless state is changed. (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 state_reason? +

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

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

Can I rate-limit state_reason? +

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

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

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