Push multiple files to a GitHub repository in a single commit
AI agents use push_files 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 |
|---|---|---|---|
repo | string | Yes | Repository name |
files | array | Yes | Array of files to push |
owner | string | Yes | Repository owner (username or organization) |
branch | string | Yes | Branch to push to (e.g., 'main' or 'master') |
message | string | Yes | Commit message |
Parameters from the server's own tool schema.
The tool creates or modifies data in a repository reversibly (commits can be reverted, files can be edited). It does not irreversibly delete data (thus not Destructive), execute arbitrary code on the user's system (thus not Execute), nor move money (thus not Financial). Write is the appropriate classification.
From the tool's definition Tool description explicitly states 'Push multiple files to a GitHub repository in a single commit' — this modifies repository content by adding or updating files.
Risk signalsAccepts file system path (files[].path) · Accepts raw HTML/template content (files[].content)
Attacks that exploit this kind of access
Push multiple files to a GitHub repository in a single commit. 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.
push_files accepts 5 parameters: repo, files, owner, branch, message. Required: repo, files, owner, branch, 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 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 Server 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 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 →