AI agents use batch_replace_and_commit_func to create or update resources in Fs Git — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fs Git environment.
This tool creates or modifies data reversibly by replacing multiple patterns in files and committing the changes via Git. While the modifications are committed (making them persistent in history), they remain reversible through standard Git operations (revert, reset), which classifies it as Write rather than Destructive.
From the tool's definition Tool name 'batch_replace_and_commit' and description 'Replace multiple patterns and commit' indicate the tool modifies file content through pattern replacement and commits changes.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Replace multiple patterns and commit. It is categorised as a Write tool in the Fs Git MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fs Git MCP server in PolicyLayer and add a rule for batch_replace_and_commit_func: 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 Fs Git. Nothing to install.
batch_replace_and_commit_func 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 batch_replace_and_commit_func 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 batch_replace_and_commit_func. 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.
batch_replace_and_commit_func is provided by the Fs Git MCP server (wojons/fs-git-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →