Create or update a file in a GitHub repository.
AI agents use createOrUpdateFile to create or update resources in GitHub MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub MCP Server environment.
This tool creates or updates files in a repository, which are reversible write operations. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or move money (would be Financial). However, the severity is high because unauthorized file modifications in a repository could corrupt source code, introduce malicious changes, or disrupt development workflows.
From the tool's definition Tool name 'createOrUpdateFile' and description 'Create or update a file in a GitHub repository' indicate reversible modification of repository content.
Attacks that exploit this kind of access
Create or update a file in a GitHub repository. It is categorised as a Write tool in the GitHub MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for createOrUpdateFile: 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 MCP Server. Nothing to install.
createOrUpdateFile 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 createOrUpdateFile 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 createOrUpdateFile. 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.
createOrUpdateFile is provided by the GitHub MCP Server MCP server (j-nowcow/github-mcp-practice). 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 →