push_files
Push multiple files to a GitHub repository in a single commit
This record as markdown: /tools/github/push-files.md
What push_files does on GitHub
AI agents use push_files 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 |
|---|---|---|---|
repo | string | — | Repository name |
files | array | — | Array of file objects to push, each object with path (string) and content (string) |
owner | string | — | Repository owner |
branch | string | — | Branch to push to |
message | string | — | Commit message |
Parameters from the server's own tool schema.
Why push_files is rated Medium
Pushing files to a repository modifies code and data in a persistent, shared location. While reversible (via git history/revert), the tool commits changes that affect the repository state and potentially trigger CI/CD pipelines or deployment workflows. This is a Write operation with high severity due to potential for accidental code corruption, security issues, or workflow disruption if an AI misuses it.
From the tool's definition Tool name 'push_files' and description 'Push multiple files to a GitHub repository in a single commit' indicate creation/modification of repository content.
Risk signalsAccepts file system path (files[].path) · Accepts raw HTML/template content (files[].content)
Attacks that exploit this kind of access
The rule that runs push_files 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 push_files, this is the rule to start with:
push_files 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 push_files call is checked against it from then on.
Questions about push_files
Push multiple files to a GitHub repository in a single commit. 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.
push_files accepts 5 parameters: repo, files, owner, branch, message. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for push_files: 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.
push_files 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 push_files 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 push_files. 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.
push_files 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.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue