# get_doc

Fetch a single documentation page as Markdown, given a product id and a page slug (both come from list_products / search_docs results, or a doc URL like /liteship/overview). Returns the title, description, a heading outline, and the full Markdown body.

Agent View of the PolicyLayer registry record for `get_doc`. HTML page: https://policylayer.com/tools/com-freebatteryfactory-docs/get-doc

## Facts

- Tool: `get_doc`
- Server: Docs (`https://freebatteryfactory.com/mcp`) — https://policylayer.com/tools/com-freebatteryfactory-docs.md
- Homepage: https://github.com/https://freebatteryfactory.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: 2 (2 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `slug` | string | yes | Page slug, e.g. "overview" or "factory" (from search_docs results or the last path segment of a doc URL). |
| `product` | string | yes | Product id from list_products (e.g. "liteship", "batpak"). |

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_doc",
    "arguments": {
      "slug": "<slug>",
      "product": "<product>"
    }
  }
}
```

## Why get_doc is rated Low

This tool retrieves and returns documentation content without creating, modifying, deleting, executing code, or affecting external systems. It is a pure read operation on static documentation pages, with no reversible or irreversible side effects. The minimal blast radius if misused is simply over-fetching documentation—no data corruption, system impact, or financial consequence.

From the tool's own definition: "Tool description explicitly states it 'Fetch[es] a single documentation page' and 'Returns the title, description, a heading outline, and the full Markdown body.' The verb 'Fetch' and the read-only nature of retrieving static documentation content with no…"

## Use case

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

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

## Other tools on Docs (3)

- `get_llms_full` — Read — https://policylayer.com/tools/com-freebatteryfactory-docs/get-llms-full.md
- `list_products` — Read — https://policylayer.com/tools/com-freebatteryfactory-docs/list-products.md
- `search_docs` — Read — https://policylayer.com/tools/com-freebatteryfactory-docs/search-docs.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-freebatteryfactory-docs · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-freebatteryfactory-docs