get-static-file-children

Lists child files and folders in a static file directory by parent path

SERVERMcp Dev SOURCE@umbraco-cms/mcp-dev

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-dev/get-static-file-children.md

WHAT IT DOES

What get-static-file-children does on Mcp Dev

AI agents call get-static-file-children to retrieve information from Mcp Dev without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get-static-file-children is rated Low

This tool retrieves directory structure information only. It has no side effects, does not execute code, does not modify data, and does not delete or move files. It is a pure read/query operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool description states it 'Lists child files and folders in a static file directory by parent path' — a query operation with no modification or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get-static-file-children safely

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

get-static-file-children Allowed

get-static-file-children is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-static-file-children": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every get-static-file-children call is checked against it from then on.

FAQ

Questions about get-static-file-children

What does the get-static-file-children tool do? +

Lists child files and folders in a static file directory by parent path. It is categorised as a Read tool in the Mcp Dev MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-static-file-children? +

Register the Mcp Dev MCP server in PolicyLayer and add a rule for get-static-file-children: 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 Dev. Nothing to install.

What risk level is get-static-file-children? +

get-static-file-children is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-static-file-children? +

Yes. Add a rate_limit block to the get-static-file-children 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 get-static-file-children completely? +

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

get-static-file-children is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 419 Mcp Dev tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →