get_file_info

Q: 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 MCP. Nothing to install.

Q: 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.

Q: 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.

Q: 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.

Q: What MCP server provides get_file_info?

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

THE RISK

Low Risk

Why get_file_info needs a policy

The tool retrieves file metadata (size, likely timestamps, permissions, etc.) without modifying, executing, or deleting anything. This is a pure read operation with minimal security risk, though it could expose filesystem information that an agent shouldn't access if the server has directory restrictions (mitigated by sibling tools like 'list_allowed_directories').

From the tool's definition Tool name 'get_file_info' and description 'Retrieve detailed metadata about a file or directory including size' indicate a query operation with no side effects.

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

POLICY

How to control get_file_info

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_file_info": {}
  }
}

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

Create a free account and register Desktop Commander MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Desktop Commander MCP tools

Destructive force_terminate Force terminate a running terminal session. Destructive kill_process Terminate a running process by PID. Use with caution as this will Execute unblock_command Remove a command from the blacklist. Once unblocked, the command can be executed normally. Execute execute_command Execute a terminal command with timeout. Command will continue running in background if it Write block_command Add a command to the blacklist. Once blocked, the command cannot be executed until unblock Write create_directory Create a new directory or ensure a directory exists. Can create multiple Write edit_block Apply surgical text replacements to files. Best for small changes (<20% of file size). Write move_file Move or rename files and directories. Can move files between directories

All 19 Desktop Commander MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_file_info

What does the get_file_info tool do? +

Retrieve detailed metadata about a file or directory including size,. It is categorised as a Read tool in the Desktop Commander MCP 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 MCP. 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 (mrgnss/claudedesktopcommander). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Desktop Commander MCP tool call.

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

CHECK YOUR STACK →