List files in a workspace, optionally filtered by computer. Use to discover files previously uploaded to a workspace; for files inside the VM
AI agents call orgo_list_files to retrieve information from Orgo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates file information from a workspace or VM without creating, modifying, or deleting any data. It has no side effects and poses minimal risk even if an AI agent explores the filesystem exhaustively. The primary risk is information disclosure of file paths and metadata, which is low severity in most contexts.
From the tool's definition Tool name is 'orgo_list_files' and description states 'List files in a workspace' with explicit purpose to 'discover files'. The verbs 'list' and 'discover' indicate retrieval without modification.
Documented attack patterns abuse exactly the kind of access orgo_list_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Orgo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for orgo_list_files:
{
"version": "1",
"default": "deny",
"tools": {
"orgo_list_files": {}
}
} orgo_list_files 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.
List files in a workspace, optionally filtered by computer. Use to discover files previously uploaded to a workspace; for files inside the VM. It is categorised as a Read tool in the Orgo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Orgo MCP Server MCP server in PolicyLayer and add a rule for orgo_list_files: 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 Orgo MCP Server. Nothing to install.
orgo_list_files 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 orgo_list_files 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 orgo_list_files. 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.
orgo_list_files is provided by the Orgo MCP Server MCP server (nickvasilescu/orgo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Orgo MCP Server, 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.
28 Orgo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.