# get_slide_deep_dive

Slide-by-slide preview of a Flevy document (a "doc-<n>" content_id). Returns every showcased slide with its name, a text description of what the slide contains (you cannot see the image, so use the description), a preview image URL, and a deep link to that slide on flevy.com. Use when a user wants to know what is inside a specific presentation before purchasing, or to reference an individual slide. Only some documents have deep dives; get_content_details reports the count.

Agent View of the PolicyLayer registry record for `get_slide_deep_dive`. HTML page: https://policylayer.com/tools/com-flevy-flevy/get-slide-deep-dive

## Facts

- Tool: `get_slide_deep_dive`
- 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 | A document content_id from search_content, e.g. "doc-1234". |

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_slide_deep_dive",
    "arguments": {
      "content_id": "<content_id>"
    }
  }
}
```

## Why get_slide_deep_dive is rated Low

This tool retrieves and displays information about existing content (slide details, descriptions, and preview URLs) without any side effects. It performs a read-only query operation on a content catalog. There is no capability to modify, execute, delete, or financially transact. The blast radius of misuse is negligible—an agent could only retrieve more preview data than intended, which causes no harm.

From the tool's own definition: "Tool 'get_slide_deep_dive' returns slide previews, descriptions, and URLs from existing documents. The description explicitly states it is used 'when a user wants to know what is inside a specific presentation before purchasing' and 'to reference an…"

## Use case

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

## Other tools on Flevy (4)

- `get_content_details` — Read — https://policylayer.com/tools/com-flevy-flevy/get-content-details.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