get_file_info
Get file or directory metadata (size, timestamps, permissions)
This record as markdown: /tools/cowork-os/get-file-info.md
What get_file_info does on CoWork OS
AI agents call get_file_info to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_file_info is rated Low
This tool queries file system metadata without modifying, executing, or deleting anything. It is purely informational and has no side effects, fitting the Read category definition (retrieves or queries data). Severity is low because metadata exposure poses minimal risk even if misused by an agent.
From the tool's definition Tool retrieves metadata only: 'size, timestamps, permissions' — no modification or execution capability described
Attacks that exploit this kind of access
The rule that runs get_file_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_file_info, this is the rule to start with:
get_file_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every get_file_info call is checked against it from then on.
Questions about get_file_info
Get file or directory metadata (size, timestamps, permissions). It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.
Register the CoWork OS 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 CoWork OS. 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 CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue