Low Risk

get_file_info

Get file/directory metadata: size, creation time, modified time, permissions, type. Only works within allowed directories.

How to control get_file_info ↓

What get_file_info does on Claude TypeScript MCP Servers

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

Low Risk

Why get_file_info needs a policy

This is a pure read operation that queries filesystem metadata. It has no side effects, cannot modify data, execute code, or trigger external operations. The 'Only works within allowed directories' restriction further limits scope. Low severity due to minimal blast radius—metadata disclosure alone poses negligible risk in development contexts.

From the tool's definition Tool retrieves file/directory metadata (size, creation time, modified time, permissions, type) without modifying, executing, or deleting any data. The description explicitly states it 'gets' information only.

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

How to control get_file_info

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude TypeScript MCP Servers, 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.

  1. Create a free account and register Claude TypeScript MCP Servers — 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 get_file_info

What does the get_file_info tool do? +

Get file/directory metadata: size, creation time, modified time, permissions, type. Only works within allowed directories. It is categorised as a Read tool in the Claude TypeScript MCP Servers MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_file_info? +

Register the Claude TypeScript MCP Servers 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 Claude TypeScript MCP Servers. 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 Claude TypeScript MCP Servers MCP server (ukkz/claude-ts-mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude TypeScript MCP Servers tool call.

Start from Claude TypeScript MCP Servers, 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.

84 Claude TypeScript MCP Servers 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.