# list_roots

List all top-level concepts in the knowledge graph with their direct children. Call this at the start of a session to get a high-level project overview.

Agent View of the PolicyLayer registry record for `list_roots`. HTML page: https://policylayer.com/tools/0xk3vin-megamemory/list-roots

## Facts

- Tool: `list_roots`
- Server: MegaMemory (`0xk3vin/megamemory`) — https://policylayer.com/tools/0xk3vin-megamemory.md
- Homepage: https://github.com/0xK3vin/MegaMemory
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_roots",
    "arguments": {}
  }
}
```

## Why list_roots is rated Low

This tool retrieves and displays existing data from the knowledge graph without creating, modifying, deleting, or executing anything. It is purely informational, making it a Read operation with low severity since unauthorized access to project structure information poses minimal direct risk.

From the tool's own definition: "Tool name 'list_roots' and description 'List all top-level concepts' indicate retrieval/querying of data. The phrase 'get a high-level project overview' confirms read-only introspection with no modifications or side effects."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches MegaMemory:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_roots": {}
  }
}
```

## Other tools on MegaMemory (8)

- `remove_concept` — Destructive — https://policylayer.com/tools/0xk3vin-megamemory/remove-concept.md
- `get_concept` — Read — https://policylayer.com/tools/0xk3vin-megamemory/get-concept.md
- `list_conflicts` — Read — https://policylayer.com/tools/0xk3vin-megamemory/list-conflicts.md
- `understand` — Read — https://policylayer.com/tools/0xk3vin-megamemory/understand.md
- `create_concept` — Write — https://policylayer.com/tools/0xk3vin-megamemory/create-concept.md
- `link` — Write — https://policylayer.com/tools/0xk3vin-megamemory/link.md
- `resolve_conflict` — Write — https://policylayer.com/tools/0xk3vin-megamemory/resolve-conflict.md
- `update_concept` — Write — https://policylayer.com/tools/0xk3vin-megamemory/update-concept.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0xk3vin-megamemory · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xk3vin-megamemory