New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_file_info

Retrieve detailed metadata about a file or directory including: - size - creation time - last modified time - permissions - type - lineCount (for text files) - lastLine (zero-indexed number of last line, for text files) - appendPosition (line number for appending, for text files) - sheets (for Ex...

SERVERDesktop Commander SOURCEwonderwhy-er/DesktopCommanderMCP
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/desktop-commander/get-file-info.md

What get_file_info does on Desktop Commander

AI agents call get_file_info to retrieve information from Desktop Commander without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_file_info is rated Low

This tool performs read-only operations that query file system metadata. It returns information about files and directories (size, timestamps, permissions, type, and content statistics) without creating, modifying, deleting, or executing anything. It has no side effects and poses minimal security risk beyond potential information disclosure about file system structure.

From the tool's definition Retrieve detailed metadata about a file or directory including: size, creation time, last modified time, permissions, type, lineCount, lastLine, appendPosition, sheets.

Questions about get_file_info

What does the get_file_info tool do? +

Retrieve detailed metadata about a file or directory including: - size - creation time - last modified time - permissions - type - lineCount (for text files) - lastLine (zero-indexed number of last line, for text files) - appendPosition (line number for appending, for text files) - sheets (for Excel files - array of {name, rowCount, colCount}) Only works within allowed directories. ${PATH_GUIDANCE} ${CMD_PREFIX_DESCRIPTION}. It is categorised as a Read tool in the Desktop Commander MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_file_info? +

Register the Desktop Commander 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 Desktop Commander. Nothing to install.

What risk level is get_file_info? +

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

Can I rate-limit get_file_info? +

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.

How do I block get_file_info completely? +

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.

What MCP server provides get_file_info? +

get_file_info is provided by the Desktop Commander MCP server (wonderwhy-er/DesktopCommanderMCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Desktop Commander, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Desktop Commander's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.