create_commit_status · Mcp Github MCP: Risk & Policy

WHAT IT DOES

What create_commit_status does on Mcp Github

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

WHY IT NEEDS A POLICY

Why create_commit_status needs a policy

This tool creates or modifies commit status objects, which is a write operation. While it affects repository metadata and CI/CD workflows, it does not delete data, execute arbitrary code, or create irreversible changes. The severity is medium because misuse could mislead developers about build status or gate invalid commits, but the action itself is non-destructive and can be corrected.

From the tool's definition Tool name 'create_commit_status' and description 'Create a status for a commit' indicate creation of new data. The status object (build passed/failed) is added to a commit but is reversible—statuses can be updated or cleared without destructive consequences.

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 Mcp Github, so you can run agents against it safely.

FAQ

Questions about create_commit_status

What does the create_commit_status tool do? +

Create a status for a commit (build passed/failed, etc.). It is categorised as a Write tool in the Mcp Github 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 Mcp Github 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 Mcp Github. 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 Mcp Github MCP server (@missionsquad/mcp-github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.