copy_directory · Windows Operations MCP: Risk & Policy

WHAT IT DOES

What copy_directory does on Windows Operations MCP

AI agents use copy_directory to create or update resources in Windows Operations MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Windows Operations MCP environment.

WHY IT NEEDS A POLICY

Why copy_directory needs a policy

Copying directories modifies the file system by creating new data structures. This is a Write operation (reversible modification) rather than Read (no side effects) or Destructive (irreversible deletion). Severity is high because uncontrolled directory copies could consume disk space, overwrite existing structures, or propagate sensitive data.

From the tool's definition Tool name 'copy_directory' indicates file system modification. Server description explicitly states 'file operations' as a capability. The tool is listed among write-class operations (copy, cp, create, create_directory) in a Windows administration context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

copy_directory Rate-limited

copy_directory 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "copy_directory": {
      "limits": [
        {
          "counter": "copy_directory_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Windows Operations MCP, so you can run agents against it safely.

FAQ

Questions about copy_directory

What does the copy_directory tool do? +

copy_directory. It is categorised as a Write tool in the Windows Operations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on copy_directory? +

Register the Windows Operations MCP server in PolicyLayer and add a rule for copy_directory: 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 Windows Operations MCP. Nothing to install.

What risk level is copy_directory? +

copy_directory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit copy_directory? +

Yes. Add a rate_limit block to the copy_directory 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.

How do I block copy_directory completely? +

Set action: deny in the PolicyLayer policy for copy_directory. 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.

What MCP server provides copy_directory? +

copy_directory is provided by the Windows Operations MCP server (sandraschi/windows-operations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.