create-or-update-file · GitHub Enterprise MCP Server MCP

WHAT IT DOES

What create-or-update-file does on GitHub Enterprise MCP Server

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

WHY IT NEEDS A POLICY

Why create-or-update-file needs a policy

Creating or updating files in a repository is a reversible modification that does not permanently destroy data or execute arbitrary code. However, the severity is high because unauthorized file modifications in a code repository could introduce malicious code, compromise production systems, alter critical configurations, or undermine repository integrity.

From the tool's definition Tool description states it 'Create or update a single file in a GitHub repository' — both create and update are Write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create-or-update-file Rate-limited

create-or-update-file 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-or-update-file": {
      "limits": [
        {
          "counter": "create-or-update-file_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 Enterprise MCP Server, so you can run agents against it safely.

FAQ

Questions about create-or-update-file

What does the create-or-update-file tool do? +

Create or update a single file in a GitHub repository. It is categorised as a Write tool in the GitHub Enterprise 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-or-update-file? +

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

What risk level is create-or-update-file? +

create-or-update-file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create-or-update-file? +

Yes. Add a rate_limit block to the create-or-update-file 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-or-update-file completely? +

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

create-or-update-file is provided by the GitHub Enterprise MCP Server MCP server (lessinthought/github-enterprice-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.