Search for patterns and replace them with new text (supports dry-run mode)
AI agents use search_and_replace to create or update resources in CodeSeeker-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CodeSeeker-MCP environment.
This tool modifies file contents by replacing matched patterns with new text, which is a reversible write operation. The dry-run mode confirms it can also perform actual writes. High severity because it can modify code across many files in a codebase. It doesn't inherently delete/destroy data (replacements can be undone), so Write is the most appropriate category rather than Destructive.
From the tool's definition 'Search for patterns and replace them with new text (supports dry-run mode)'
Documented attack patterns abuse exactly the kind of access search_and_replace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CodeSeeker-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_and_replace:
{
"version": "1",
"default": "deny",
"tools": {
"search_and_replace": {
"limits": [
{
"counter": "search_and_replace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} search_and_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.
Search for patterns and replace them with new text (supports dry-run mode). It is categorised as a Write tool in the CodeSeeker-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CodeSeeker- MCP server in PolicyLayer and add a rule for search_and_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 CodeSeeker-MCP. Nothing to install.
search_and_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 search_and_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 search_and_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.
search_and_replace is provided by the CodeSeeker- MCP server (mixelpixx/codeseeker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CodeSeeker-MCP, 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.
12 CodeSeeker-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.