push_files

Push multiple files to a GitHub repository in a single commit

Accepts file system path (files[].path); Accepts raw HTML/template content (files[].content); Single-target operation

Part of the GitHub API MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents use push_files to create or modify resources in GitHub API MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON PUSH_FILES

Without a policy, an AI agent could call push_files repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach GitHub API MCP Server.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

lowkeyrd-servers.yaml

tools:
  push_files:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full GitHub API MCP Server policy for all 26 tools.

// DETAILS

Tool Name push_files

Category Write

MCP Server GitHub API MCP Server MCP Server

Risk Level Medium

// MORE GITHUB API MCP SERVER TOOLS

Write add_issue_comment Write create_branch Write create_issue Write create_or_update_file Write create_pull_request Write create_pull_request_review Write create_repository Write merge_pull_request

View all 26 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like push_files have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the push_files tool do? +

Push multiple files to a GitHub repository in a single commit. It is categorised as a Write tool in the GitHub API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on push_files? +

Add a rule in your Intercept YAML policy under the tools section for push_files. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the GitHub API MCP Server MCP server.

What risk level is push_files? +

push_files is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit push_files? +

Yes. Add a rate_limit block to the push_files rule in your Intercept 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.

How do I block push_files completely? +

Set action: deny in the Intercept 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.

What MCP server provides push_files? +

push_files is provided by the GitHub API MCP Server MCP server (lowkeyrd/servers). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

push_files

Enforce policies on GitHub API MCP Server