Perform multiple search and replace operations in a single command
AI agents use bulk_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 performs search-and-replace operations that modify file contents. While replacements are theoretically reversible (via version control or undo), the tool itself enables write operations at scale. The bulk nature means a single invocation can modify multiple files/locations, increasing the risk of unintended modifications.
From the tool's definition 'Perform multiple search and replace operations' - directly modifies file contents through replacement operations. The description indicates this tool creates or modifies data (matches Write category).
Documented attack patterns abuse exactly the kind of access bulk_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 bulk_replace:
{
"version": "1",
"default": "deny",
"tools": {
"bulk_replace": {
"limits": [
{
"counter": "bulk_replace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} bulk_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.
Perform multiple search and replace operations in a single command. 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 bulk_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.
bulk_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 bulk_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 bulk_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.
bulk_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.