# get_content_details

Full metadata for one Flevy item, by content_id from search_content (e.g. "doc-1234" or "case-567"). Documents return the author with their credentials (headline, bio, LinkedIn, profile URL; pass the author name to search_content's author filter to list more of their documents), full description, editor summary, AI summary, and editorial review when available, page/slide count, price, FlevyPro inclusion, management topics, ranking badge, and the number of slide deep dives available. Case studies return the client situation, TL;DR, and summary. Call this before recommending an item so you can describe it accurately and cite the author's credentials, and share the returned flevy.com URL.

Agent View of the PolicyLayer registry record for `get_content_details`. HTML page: https://policylayer.com/tools/com-flevy-flevy/get-content-details

## Facts

- Tool: `get_content_details`
- 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: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `content_id` | string | yes | The content_id from search_content: "doc-<n>" for documents, "case-<n>" for case studies. |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_content_details",
    "arguments": {
      "content_id": "<content_id>"
    }
  }
}
```

## Why get_content_details is rated Low

This tool only retrieves and queries detailed information about existing consulting documents and case studies. It has no ability to create, modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could only read information about available consulting frameworks and templates without side effects.

From the tool's own definition: "Tool description states it retrieves 'Full metadata for one Flevy item' including author credentials, description, summary, page/slide count, price, topics, ranking, and availability of deep dives."

## Use case

AI agents call get_content_details 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": {
    "get_content_details": {}
  }
}
```

## Other tools on Flevy (4)

- `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
- `list_topics` — Read — https://policylayer.com/tools/com-flevy-flevy/list-topics.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