AI agents call get_file_info to retrieve information from MCP File Edit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves file metadata (size, permissions, timestamps, etc.) with no side effects or state changes. It is a pure read operation with minimal security risk—an AI agent cannot misuse it to cause harm beyond potential information disclosure of file metadata, which is typically low-impact.
From the tool's definition Tool name 'get_file_info' and description 'Get detailed file information' indicate retrieval of metadata without modification. The server description lists 'reading' as a capability, and this tool performs no write, delete, or execute operations.
Documented attack patterns abuse exactly the kind of access get_file_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP File Edit, and nothing reaches the server without passing your rules. This is the rule we recommend for get_file_info:
{
"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.
Free to start. No card required.
Get detailed file information. It is categorised as a Read tool in the MCP File Edit MCP Server, which means it retrieves data without modifying state.
Register the MCP File Edit 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 MCP File Edit. 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 MCP File Edit MCP server (patrickomatik/mcp-file-edit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP File Edit, 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.
32 MCP File Edit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.