AI agents use replace_in_files to create or update resources in MCP File Edit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP File Edit environment.
The 'replace_in_files' tool modifies file contents in place, which is a reversible write operation (files can be restored from backups or version control). This is less severe than deletion but more severe than simple reads. Severity is 'high' because mass replacement across files could corrupt critical code, configurations, or data if an AI agent misapplies the tool with incorrect search/replace patterns.
From the tool's definition Tool name 'replace_in_files' indicates modification of file contents. Server description states 'writing' and 'patching' capabilities. Sibling tools include 'delete_file' and 'git' operations, confirming this server handles destructive and write operations.
Documented attack patterns abuse exactly the kind of access replace_in_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP File Edit, and nothing reaches the server without passing your rules. This is the rule we recommend for replace_in_files:
{
"version": "1",
"default": "deny",
"tools": {
"replace_in_files": {
"limits": [
{
"counter": "replace_in_files_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}replace_in_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.
replace_in_files. It is categorised as a Write tool in the MCP File Edit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP File Edit MCP server in PolicyLayer and add a rule for replace_in_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 MCP File Edit. Nothing to install.
replace_in_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 replace_in_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 replace_in_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.
replace_in_files is provided by the MCP File Edit MCP server (patrickomatik/mcp-file-edit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP File Edit, 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.
32 MCP File Edit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.