Low Risk

stat_items

Get detailed status information for multiple specified paths.

How to control stat_items ↓

What stat_items does on Filesystem

AI agents call stat_items to retrieve information from Filesystem without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why stat_items needs a policy

The stat_items tool queries and returns status information (permissions, size, timestamps, etc.) about filesystem items. This is a read-only operation with no side effects, and falls squarely into the Read category. The presence of destructive tools like delete_items and write tools like replace_content on the same server does not change this tool's classification.

From the tool's definition Tool name 'stat_items' and description 'Get detailed status information for multiple specified paths' indicates retrieval of file/directory metadata without modification or deletion.

Documented attack patterns abuse exactly the kind of access stat_items gives an agent:

How to control stat_items

PolicyLayer is an MCP gateway — it sits between your AI agents and Filesystem, and nothing reaches the server without passing your rules. This is the rule we recommend for stat_items:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "stat_items": {}
  }
}

stat_items is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Filesystem — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about stat_items

What does the stat_items tool do? +

Get detailed status information for multiple specified paths. It is categorised as a Read tool in the Filesystem MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on stat_items? +

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

What risk level is stat_items? +

stat_items is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit stat_items? +

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

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

stat_items is provided by the Filesystem MCP server (sylphxai/filesystem-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Filesystem tool call.

Start from Filesystem, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

13 Filesystem tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.