AI agents use batch_move_files 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.
Moving files is a reversible Write operation that modifies data location and organization without deletion. While the parallel batch nature increases blast radius (high severity), the operation remains reversible—files can be moved back. This is less severe than Destructive (which would be irreversible deletion), but more impactful than simple Read operations.
From the tool's definition Tool name 'batch_move_files' and description 'Move multiple files in parallel' indicates file relocation operations that modify filesystem state.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_move_files 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_move_files:
{
"version": "1",
"default": "deny",
"tools": {
"batch_move_files": {
"limits": [
{
"counter": "batch_move_files_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}batch_move_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.
Move multiple files in parallel. 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_move_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 OODA Computer Control. Nothing to install.
batch_move_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 batch_move_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 batch_move_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.
batch_move_files 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.