Create or update multiple files in a single commit using the Git Data API
AI agents use push_multiple_files to create or update resources in Gitbridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitbridge environment.
This tool creates or updates data (files in a git repository) without irreversible deletion. While git history is immutable, the working tree changes are reversible via revert/reset operations, placing it in Write rather than Destructive. Severity is high due to the potential blast radius: an agent could modify multiple critical files in production code simultaneously, affecting many users or systems.
From the tool's definition Tool description explicitly states 'Create or update multiple files' indicating reversible modifications to repository content. Sibling context shows this is part of a file operations suite (alongside create_repo, delete_file, move_file).
Documented attack patterns abuse exactly the kind of access push_multiple_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gitbridge, and nothing reaches the server without passing your rules. This is the rule we recommend for push_multiple_files:
{
"version": "1",
"default": "deny",
"tools": {
"push_multiple_files": {
"limits": [
{
"counter": "push_multiple_files_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}push_multiple_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.
Free to start. No card required.
Create or update multiple files in a single commit using the Git Data API. It is categorised as a Write tool in the Gitbridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gitbridge MCP server in PolicyLayer and add a rule for push_multiple_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 Gitbridge. Nothing to install.
push_multiple_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_multiple_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_multiple_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_multiple_files is provided by the Gitbridge MCP server (iotus/gitbridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gitbridge, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Gitbridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.