create_or_update_file

THE RISK

Medium Risk

Why create_or_update_file needs a policy

This tool modifies repository data by creating new files or updating existing ones. These are reversible operations (files can be deleted or reverted), so it falls under Write rather than Destructive. The severity is medium because misuse could corrupt repository content, introduce malicious code, or overwrite important files, but the effects are recoverable through version control.

From the tool's definition Tool description explicitly states 'Create or update a single file in a GitHub repository'. The verbs 'create' and 'update' are reversible modifications of repository content.

Documented attack patterns abuse exactly the kind of access create_or_update_file gives an agent:

POLICY

How to control create_or_update_file

PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub MCP Server Plus, and nothing reaches the server without passing your rules. This is the rule we recommend for create_or_update_file:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_or_update_file": {
      "limits": [
        {
          "counter": "create_or_update_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register GitHub MCP Server Plus — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GitHub MCP Server Plus tools

Write add_issue_comment Add a comment to an existing issue Write create_branch Create a new branch in a GitHub repository Write create_issue Create a new issue in a GitHub repository Write create_pull_request Create a new pull request in a GitHub repository Write create_repository Create a new GitHub repository in your account Write fork_repository Fork a GitHub repository to your account or specified organization Write push_files_content Push multiple files with direct content to a GitHub repository in a single commit Write push_files_from_path Push multiple files from filesystem paths to a GitHub repository in a single commit

All 18 GitHub MCP Server Plus tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_or_update_file

What does the create_or_update_file tool do? +

Create or update a single file in a GitHub repository. It is categorised as a Write tool in the GitHub MCP Server Plus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_or_update_file? +

Register the GitHub MCP Server Plus MCP server in PolicyLayer and add a rule for create_or_update_file: 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 Plus. Nothing to install.

What risk level is create_or_update_file? +

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

Can I rate-limit create_or_update_file? +

Yes. Add a rate_limit block to the create_or_update_file 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 create_or_update_file completely? +

Set action: deny in the PolicyLayer policy for create_or_update_file. 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 create_or_update_file? +

create_or_update_file is provided by the GitHub MCP Server Plus MCP server (phialsbasement/mcp-github-server-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GitHub MCP Server Plus tool call.

Start from GitHub MCP Server Plus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →