AI agents call file_info to retrieve information from Awesome-MCP-Scaffold 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 without modifying, executing, or deleting any data. It falls squarely into the Read category as a query/fetch operation. Severity is low because exposing file information has minimal blast radius—an AI misuse would likely result in information disclosure rather than data loss or system compromise.
From the tool's definition Tool name is 'file_info' with description 'Get file information'. The verb 'Get' and the informational nature of retrieving file metadata (size, timestamps, permissions, etc.) indicates a read-only operation with no side effects.
Documented attack patterns abuse exactly the kind of access file_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Awesome-MCP-Scaffold, and nothing reaches the server without passing your rules. This is the rule we recommend for file_info:
{
"version": "1",
"default": "deny",
"tools": {
"file_info": {}
}
}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 file information. It is categorised as a Read tool in the Awesome-MCP-Scaffold MCP Server, which means it retrieves data without modifying state.
Register the Awesome-MCP-Scaffold MCP server in PolicyLayer and add a rule for 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 Awesome-MCP-Scaffold. Nothing to install.
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 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 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.
file_info is provided by the Awesome-MCP-Scaffold MCP server (ww-ai-lab/awesome-mcp-scaffold). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Awesome-MCP-Scaffold, 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.
24 Awesome-MCP-Scaffold tools catalogued and risk-classified — across an index of 43,000+ MCP servers.