FileSystem

Manages file system operations with eight modes:

SERVERWindows-MCP SOURCE13888285815/windows-mcp

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/13888285815-windows-mcp/filesystem.md

WHAT IT DOES

What FileSystem does on Windows-MCP

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

RISK

Why FileSystem is rated Critical

File system management tools typically include operations ranging from read (list, get) to destructive (delete, overwrite). Given the server's context — native Windows OS interaction, application control, and the presence of highly privileged sibling tools like PowerShell and Registry — this tool almost certainly includes destructive operations such as delete or overwrite alongside read/write modes.

From the tool's definition 'Manages file system operations with eight modes' on a Windows OS automation server with sibling tools including PowerShell, Registry, and Process

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs FileSystem safely

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

FileSystem Hidden

FileSystem 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": [
    "FileSystem"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about FileSystem

What does the FileSystem tool do? +

Manages file system operations with eight modes:. It is categorised as a Destructive tool in the Windows-MCP 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 FileSystem? +

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

What risk level is FileSystem? +

FileSystem 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 FileSystem? +

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

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

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

KEEP EXPLORING

More on Windows, and thousands of servers like it.

This server

All 18 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 →