# list_topics

The canonical list of management topics Flevy's catalog is organized under, each with its known aliases (e.g. "Digital Transformation" and "Digital Transformation Strategy" may be the same topic) and content counts. Use this to map a user's phrasing to the exact topic filter accepted by search_content, or to show what subject areas Flevy covers.

Agent View of the PolicyLayer registry record for `list_topics`. HTML page: https://policylayer.com/tools/com-flevy-flevy/list-topics

## Facts

- Tool: `list_topics`
- Server: Flevy (`https://flevy.com/mcp`) — https://policylayer.com/tools/com-flevy-flevy.md
- Homepage: https://github.com/https://flevy.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- 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_topics",
    "arguments": {}
  }
}
```

## Why list_topics is rated Low

This tool retrieves and queries data from Flevy's topic taxonomy without modifying, executing code, deleting content, or moving money. It has no side effects beyond returning information. It is purely informational for navigation and filtering purposes.

From the tool's own definition: "Tool description explicitly states it provides 'The canonical list of management topics' and is used to 'map a user's phrasing to the exact topic filter' and 'show what subject areas Flevy covers.' Keywords: 'list,' 'map,' and 'show' indicate read-only…"

## Use case

AI agents call list_topics to retrieve information from Flevy 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 Flevy:

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

## Other tools on Flevy (4)

- `get_content_details` — Read — https://policylayer.com/tools/com-flevy-flevy/get-content-details.md
- `get_slide_deep_dive` — Read — https://policylayer.com/tools/com-flevy-flevy/get-slide-deep-dive.md
- `get_topic_details` — Read — https://policylayer.com/tools/com-flevy-flevy/get-topic-details.md
- `search_content` — Read — https://policylayer.com/tools/com-flevy-flevy/search-content.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=com-flevy-flevy · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-flevy-flevy
