get_file_info

THE RISK

Low Risk

Why get_file_info needs a policy

This tool performs a read-only operation to fetch file/directory metadata. It has no side effects, does not execute code, does not modify or delete data, and does not affect financial systems. While it could expose sensitive metadata, the risk is limited to information disclosure without system state changes, fitting the 'Read' category with low severity.

From the tool's definition Tool name is 'get_file_info' and description states 'Retrieve detailed metadata about a file or directory. Returns comprehensive' — retrieval operations with no modification capability.

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 Filesystem MCP Server SSE, 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 Filesystem MCP Server SSE — 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 Filesystem MCP Server SSE tools

Write create_directory Create a new directory or ensure a directory exists. Can create multiple Write edit_file Make line-based edits to a text file. Each edit replaces exact line sequences Write move_file Move or rename files and directories. Can move files between directories Write write_file Create a new file or completely overwrite an existing file with new content. Read directory_tree Get a recursive tree view of files and directories as a JSON structure. Read list_allowed_directories Returns the list of directories that this server is allowed to access. Read list_directory Get a detailed listing of all files and directories in a specified path. Read read_file Read the complete contents of a file from the file system.

All 11 Filesystem MCP Server SSE 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. Returns comprehensive. It is categorised as a Read tool in the Filesystem MCP Server SSE MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_file_info? +

Register the Filesystem MCP Server SSE 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 MCP Server SSE. 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 Filesystem MCP Server SSE MCP server (ysthink/filesystem-mcp-server-sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Filesystem MCP Server SSE tool call.

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

CHECK YOUR STACK →