push-files · GitHub Enterprise MCP Server MCP: Risk & Policy

WHAT IT DOES

What push-files does on GitHub Enterprise MCP Server

AI agents use push-files to create or update resources in GitHub Enterprise MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub Enterprise MCP Server environment.

WHY IT NEEDS A POLICY

Why push-files needs a policy

This tool creates or modifies data (files and commits) in a repository. It is reversible—commits can be reverted or reset—so it does not qualify as Destructive. It does not execute arbitrary code, run shell commands, or have financial impact. Write is the appropriate category because the tool's primary effect is to commit file changes, which modifies repository state in a way that can be undone.

From the tool's definition Tool name is 'push-files' and description states it 'Push[es] multiple files to a GitHub repository in a single commit'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

push-files Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "push-files": {
      "limits": [
        {
          "counter": "push-files_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GitHub Enterprise MCP Server, so you can run agents against it safely.

FAQ

Questions about push-files

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 Enterprise 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? +

Register the GitHub Enterprise MCP Server 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 Enterprise MCP Server. Nothing to install.

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 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.

How do I block push-files completely? +

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.

What MCP server provides push-files? +

push-files is provided by the GitHub Enterprise MCP Server MCP server (lessinthought/github-enterprice-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.