AI agents call stat_tree to retrieve information from MCP Files without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
stat_tree retrieves and aggregates metadata about the filesystem (counts, sizes) without side effects. It is clearly a read-only operation that queries filesystem statistics, making it a Read category tool with low severity since misuse would only expose filesystem information, not cause data loss or execute arbitrary operations.
From the tool's definition Tool performs a filesystem tree walk that 'report[s] aggregate file/dir counts and total bytes' without modification. The verb 'report' and the nature of the operation (gathering statistics) indicate data retrieval only.
Attacks that exploit this kind of access
Walk a subtree (optionally limited by depth) and report aggregate file/dir counts and total bytes, excluding .metadata. It is categorised as a Read tool in the MCP Files MCP Server, which means it retrieves data without modifying state.
Register the MCP Files MCP server in PolicyLayer and add a rule for stat_tree: 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 Files. Nothing to install.
stat_tree 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 stat_tree 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 stat_tree. 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.
stat_tree is provided by the MCP Files MCP server (tspspi/mcpfiles). 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 →