AI agents call get-static-file-children to retrieve information from Mcp Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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
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.
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.
get-static-file-children is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →