create_commit_status · GitHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_commit_status does on GitHub MCP Server

AI agents use create_commit_status to create or update resources in GitHub MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub MCP Server environment.

WHY IT NEEDS A POLICY

Why create_commit_status needs a policy

This tool creates/modifies commit status records, which are data structures attached to commits. While not permanently destructive (statuses can be updated or cleared), it irreversibly commits information to the repository's commit history and affects automated workflows and merge decisions. This is a Write operation rather than Read (it modifies state) or Execute (it doesn't run arbitrary code).

From the tool's definition Tool name 'create_commit_status' indicates creation of a commit status record. GitHub commit statuses are used to report build/test results and CI/CD pipeline states on commits.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_commit_status Rate-limited

create_commit_status stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_commit_status": {
      "limits": [
        {
          "counter": "create_commit_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GitHub MCP Server, so you can run agents against it safely.

FAQ

Questions about create_commit_status

What does the create_commit_status tool do? +

create_commit_status. It is categorised as a Write tool in the GitHub MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_commit_status? +

Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for create_commit_status: 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 MCP Server. Nothing to install.

What risk level is create_commit_status? +

create_commit_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_commit_status? +

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

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

create_commit_status is provided by the GitHub MCP Server MCP server (software-engineer-mj/github-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.