list_tree

What list_tree does on Allcanuse

AI agents call list_tree to retrieve information from Allcanuse without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_tree is rated Low

Despite the empty description lowering confidence, the tool name strongly implies a directory listing or tree-viewing operation, which retrieves information without modifying data. The server context (system management tools) supports this interpretation. Classified as Read with low severity due to information disclosure risk being limited compared to command execution or data modification.

From the tool's definition Tool name 'list_tree' suggests listing/traversing a directory or file structure tree. No description provided, but the name pattern aligns with read-only operations like 'ls -R' or file tree traversal.

The rule that runs list_tree safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Allcanuse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_tree, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_tree": {}
  }
}

Questions about list_tree