Extract comprehensive metadata and statistics for files or directories.
AI agents call get_file_info to retrieve information from Vulcan File Ops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries file/directory metadata and statistics without creating, modifying, deleting, or executing anything. It has no side effects beyond reading filesystem metadata. Severity is low because even if an AI agent misuses it, the blast radius is limited to information disclosure about file system structure, which poses minimal direct risk.
From the tool's definition Tool name is 'get_file_info' and description states it 'Extract[s] comprehensive metadata and statistics for files or directories'—purely informational retrieval with no modification capability.
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 Vulcan File Ops, 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.
Extract comprehensive metadata and statistics for files or directories. It is categorised as a Read tool in the Vulcan File Ops MCP Server, which means it retrieves data without modifying state.
Register the Vulcan File Ops 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 Vulcan File Ops. 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 Vulcan File Ops MCP server (n0zer0d4y/vulcan-file-ops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vulcan File Ops, 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.
15 Vulcan File Ops tools catalogued and risk-classified — across an index of 43,000+ MCP servers.