get_file_info
Retrieve detailed metadata about a file or directory. Returns comprehensive information including size, creation time, last modified time, permissions, and type. This tool is perfect for understanding file characteristics without reading the actual content. Only works within allowed directories.
This record as markdown: /tools/filesystem/get-file-info.md
What get_file_info does on Filesystem
AI agents call get_file_info to retrieve information from Filesystem without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes |
Parameters from the server's own tool schema.
Why get_file_info is rated Low
This tool only retrieves and queries file metadata without side effects. It does not create, modify, delete, or execute anything. The explicit statement that it works 'without reading the actual content' and only returns metadata properties (size, timestamps, permissions) confirms it is a purely informational read operation with minimal security impact.
From the tool's definition Tool description states it 'Retrieve[s] detailed metadata about a file or directory' and is 'perfect for understanding file characteristics without reading the actual content.' Returns 'size, creation time, last modified time, permissions, and type.' No…
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs get_file_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Filesystem, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_file_info, this is the rule to start with:
get_file_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Filesystem, apply this rule, and every get_file_info call is checked against it from then on.
Questions about get_file_info
Retrieve detailed metadata about a file or directory. Returns comprehensive information including size, creation time, last modified time, permissions, and type. This tool is perfect for understanding file characteristics without reading the actual content. Only works within allowed directories. It is categorised as a Read tool in the Filesystem MCP Server, which means it retrieves data without modifying state.
get_file_info accepts 1 parameter: path. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Filesystem MCP server in PolicyLayer and add a rule for get_file_info: 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.
get_file_info 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_file_info 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_file_info. 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_file_info is provided by the Filesystem MCP server (@modelcontextprotocol/server-filesystem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Filesystem, and thousands of servers like it.
This server
Across the catalogue