create_or_update_file
A write tool on the GitHub MCP server.
This record as markdown: /tools/io-github-aifity-omnigit-mcp/create-or-update-file.md
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.
Why create_or_update_file is rated Medium
This tool creates or modifies files in a repository, which are reversible operations (files can be deleted or reverted via version control). It does not irreversibly destroy data, so it is Write rather than Destructive.
From the tool's definition Tool explicitly described as 'Create or update file' - directly modifies repository content by creating new files or updating existing ones.
Attacks that exploit this kind of access
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 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.
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.
Questions about create_or_update_file
create_or_update_file is a write tool on the GitHub MCP server. 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.
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.
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 GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue