Create or update a single file in a GitHub repository
AI agents use create_or_update_file to create or update resources in Server Github — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Server Github environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
sha | string | — | SHA of the file being replaced (required when updating existing files) |
path | string | Yes | Path where to create/update the file |
repo | string | Yes | Repository name |
owner | string | Yes | Repository owner (username or organization) |
branch | string | Yes | Branch to create/update the file in |
content | string | Yes | Content of the file |
message | string | Yes | Commit message |
Parameters from the server's own tool schema.
This tool creates new files or modifies existing ones in a GitHub repository, which are reversible write operations. While the changes persist in version control and could affect production code if misused by an AI agent, they are not destructive (files remain in history), not financial, and not executable in themselves.
From the tool's definition Tool name is 'create_or_update_file' and description states it will 'Create or update a single file in a GitHub repository'. This directly modifies repository content.
Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (content)
Attacks that exploit this kind of access
Create or update a single file in a GitHub repository. It is categorised as a Write tool in the Server Github MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_or_update_file accepts 7 parameters: sha, path, repo, owner, branch, content, message. Required: path, repo, owner, branch, content, message. The full parameter table on this page comes from the server's own tool schema.
Register the Server 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 Server Github. Nothing to install.
create_or_update_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
create_or_update_file is provided by the Server Github MCP server (@iflow-mcp/server-github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →