Move or rename a file. Reads from old path, writes to new path, then returns a GitHub link for the user to manually delete the original.
AI agents use move_file 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 modifies the repository state by creating a file at a new location, which is a reversible write operation. While it suggests manual deletion of the original, that deletion is not performed by the tool itself. The operation is not destructive (not automatic deletion), not financial, and not arbitrary code execution—it's a controlled file operation.
From the tool's definition Tool description states it 'Reads from old path, writes to new path' - it creates new data (the file at the new path) reversibly. The manual deletion step means the old file is not automatically removed by this tool.
Documented attack patterns abuse exactly the kind of access move_file 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 move_file:
{
"version": "1",
"default": "deny",
"tools": {
"move_file": {
"limits": [
{
"counter": "move_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_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.
Free to start. No card required.
Move or rename a file. Reads from old path, writes to new path, then returns a GitHub link for the user to manually delete the original. 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 move_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 Gitbridge. Nothing to install.
move_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 move_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 move_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.
move_file 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.