github_create_or_update_file
A write tool on the Integrations MCP server.
This record as markdown: /tools/shriram-vasudevan-integrations-mcp/github-create-or-update-file.md
What github_create_or_update_file does on Integrations MCP
AI agents use github_create_or_update_file to create or update resources in Integrations MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Integrations MCP environment.
Why github_create_or_update_file is rated Medium
This tool modifies repository contents by creating new files or updating existing ones. While reversible (can be undone via git operations), it poses significant risk if an AI agent pushes malicious code, alters critical files, or modifies documentation without authorization. The high severity reflects potential for code injection, intellectual property theft, or supply chain compromise.
From the tool's definition Tool name 'github_create_or_update_file' explicitly indicates file creation and modification capabilities on GitHub repositories. The verb 'create_or_update' confirms reversible write operations.
Attacks that exploit this kind of access
The rule that runs github_create_or_update_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_create_or_update_file, this is the rule to start with:
github_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every github_create_or_update_file call is checked against it from then on.
Questions about github_create_or_update_file
github_create_or_update_file is a write tool on the Integrations MCP server. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Integrations MCP server in PolicyLayer and add a rule for github_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 Integrations MCP. Nothing to install.
github_create_or_update_file 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 github_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.
Set action: deny in the PolicyLayer policy for github_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.
github_create_or_update_file is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Integrations, and thousands of servers like it.
This server
Across the catalogue