Apply multiple search/replace operations to a single file sequentially. Each edit operates on the result of the previous edit. Supports partial success - completed edits are saved even if later edits fail. Use stopOnError to halt on first failure. Use dryRun for preview.
AI agents use batch_edit_blocks to create or update resources in OODA Computer Control — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OODA Computer Control environment.
This tool modifies file content through search/replace operations. While the changes are theoretically reversible (files can be restored from backups or version control), the tool itself enables direct data modification without deletion. This is a Write operation rather than Destructive because the modifications are reversible and not inherently irreversible.
From the tool's definition Tool description states it 'Apply[s] multiple search/replace operations to a single file sequentially' and 'completed edits are saved even if later edits fail', indicating it modifies file content.
Documented attack patterns abuse exactly the kind of access batch_edit_blocks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OODA Computer Control, and nothing reaches the server without passing your rules. This is the rule we recommend for batch_edit_blocks:
{
"version": "1",
"default": "deny",
"tools": {
"batch_edit_blocks": {
"limits": [
{
"counter": "batch_edit_blocks_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}batch_edit_blocks 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.
Apply multiple search/replace operations to a single file sequentially. Each edit operates on the result of the previous edit. Supports partial success - completed edits are saved even if later edits fail. Use stopOnError to halt on first failure. Use dryRun for preview. It is categorised as a Write tool in the OODA Computer Control MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OODA Computer Control MCP server in PolicyLayer and add a rule for batch_edit_blocks: 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 OODA Computer Control. Nothing to install.
batch_edit_blocks 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_edit_blocks 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_edit_blocks. 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_edit_blocks is provided by the OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OODA Computer Control, 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.
99 OODA Computer Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.