AI agents use easy_replace to create or update resources in ZMCPTools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ZMCPTools environment.
The tool performs file modifications through fuzzy string replacement. While reversible (files can be restored from backups or version control), it can alter critical code or configuration files. The 'fuzzy' matching aspect introduces risk of unintended replacements affecting wrong targets. Medium severity reflects the reversible nature but acknowledges potential for disruption if applied to wrong files or patterns.
From the tool's definition Tool description explicitly states 'replacement in files', which involves modifying file content. This is a write operation that creates or modifies data reversibly.
Documented attack patterns abuse exactly the kind of access easy_replace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZMCPTools, and nothing reaches the server without passing your rules. This is the rule we recommend for easy_replace:
{
"version": "1",
"default": "deny",
"tools": {
"easy_replace": {
"limits": [
{
"counter": "easy_replace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}easy_replace 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.
Fuzzy string replacement in files with smart matching. It is categorised as a Write tool in the ZMCPTools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for easy_replace: 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 ZMCPTools. Nothing to install.
easy_replace 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 easy_replace 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 easy_replace. 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.
easy_replace is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
70 ZMCPTools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.