create_or_update_file

SERVERGitHub SOURCEoci:ghcr.io/github/github-mcp-server:1.3.0

Medium RISK CLASS

Category Write

Parameters 70 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/github/create-or-update-file.md

WHAT IT DOES

What create_or_update_file does on GitHub

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

Parameter	Type	Required	Description
`sha`	string	—	The blob SHA of the file being replaced. Required if the file already exists.
`path`	string	—	Path where to create/update the file
`repo`	string	—	Repository name
`owner`	string	—	Repository owner (username or organization)
`branch`	string	—	Branch to create/update the file in
`content`	string	—	Content of the file
`message`	string	—	Commit message

Parameters from the server's own tool schema.

RISK

Why create_or_update_file is rated Medium

This tool modifies repository state by creating new files or updating existing ones. While reversible (changes can be undone via version control), the ability to modify code in a live repository poses significant risk if misused by an AI agent, such as injecting malicious code, breaking builds, or corrupting important files.

From the tool's definition Tool name explicitly states 'create_or_update_file' and description confirms it 'Create or update a single file in a GitHub repository.' These are reversible write operations.

Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (content)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

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.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every create_or_update_file call is checked against it from then on.

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. If updating, you should provide the SHA of the file you want to update. Use this tool to create or update a file in a GitHub repository remotely; do not use it for local file operations. In order to obtain the SHA of original file version before updating, use the following git command: git rev-parse <branch>:<path to file> SHA MUST be provided for existing file updates. It is categorised as a Write tool in the GitHub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create_or_update_file accept? +

create_or_update_file accepts 7 parameters: sha, path, repo, owner, branch, content, message. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_or_update_file? +

Register the GitHub 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. 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 MCP server (oci:ghcr.io/github/github-mcp-server:1.3.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 86 GitHub tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →