sync_directories

Synchronize two directories with different modes

SERVERMcp Windows SOURCEmukul975/mcp-windows-automation

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mukul975-mcp-windows-automation/sync-directories.md

WHAT IT DOES

What sync_directories does on Mcp Windows

AI agents call sync_directories to permanently remove resources in Mcp Windows, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why sync_directories is rated Critical

Directory synchronization typically involves overwriting or deleting files in the destination to match the source. Depending on the sync mode, files in the target directory may be irreversibly deleted or overwritten. The mention of 'different modes' suggests options that could include destructive mirroring (deleting files not present in source).

From the tool's definition Synchronize two directories with different modes

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sync_directories safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Windows, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sync_directories, this is the rule to start with:

sync_directories Hidden

sync_directories is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "sync_directories"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Windows, apply this rule, and every sync_directories call is checked against it from then on.

FAQ

Questions about sync_directories

What does the sync_directories tool do? +

Synchronize two directories with different modes. It is categorised as a Destructive tool in the Mcp Windows MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on sync_directories? +

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

What risk level is sync_directories? +

sync_directories is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit sync_directories? +

Yes. Add a rate_limit block to the sync_directories 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 sync_directories completely? +

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

sync_directories is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Windows, and thousands of servers like it.

This server

All 441 Mcp Windows tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →