AI agents call file_statistics to retrieve information from Astro MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns file system metadata and statistics without creating, modifying, deleting, or executing any operations. It is a pure read operation analogous to 'ls' or 'du' commands. The low severity reflects minimal risk even if misused by an agent, as it only exposes informational metadata about files already present on the system.
From the tool's definition Tool name 'file_statistics' combined with description stating it retrieves 'comprehensive file system statistics including storage usage, file counts by type/source, and recent files' indicates data retrieval with no modification or deletion capabilities.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get comprehensive file system statistics including storage usage, file counts by type/source, and recent files across all data sources. It is categorised as a Read tool in the Astro MCP MCP Server, which means it retrieves data without modifying state.
Register the Astro MCP server in PolicyLayer and add a rule for file_statistics: 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 Astro MCP. Nothing to install.
file_statistics 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 file_statistics 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 file_statistics. 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.
file_statistics is provided by the Astro MCP server (sandyyuan/astro_mcp). 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 →