# docs

Start here — frisian-mcp documentation and server guide. Actions: about (server identity and links), getting_started (step-by-step adoption guide), integrations (Django/DRF config reference), security (auth model, OAuth, API keys, tiers), demo (explore the live demo endpoints), documents (browse all documentation articles), rag (semantic and full-text doc search).

Agent View of the PolicyLayer registry record for `docs`. HTML page: https://policylayer.com/tools/com-frisian-mcp-django/docs

## Facts

- Tool: `docs`
- Server: Frisian MCP (Django) (`https://mcp.frisian-mcp.com/mcp/`) — https://policylayer.com/tools/com-frisian-mcp-django.md
- Homepage: https://github.com/Frisian-MCP/frisian-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `action` | string | no | Operation to perform. Omit or use 'help' to list all available actions and their required parameters. |
| `params` | object | no | Action-specific parameters. about: {version}; getting_started: {version}; integrations: {version}; security: {version}; demo: {surface}; documents: {sub_action, |

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

## Why docs is rated Low

This tool exclusively retrieves and presents documentation content. The actions listed (about, getting_started, integrations, security, demo, documents, rag) are all informational/read operations that query or display existing documentation. There are no side effects, no code execution, no data modifications, and no destructive operations.

From the tool's own definition: "Tool description states it provides documentation and guides: 'about', 'getting_started', 'integrations', 'security', 'demo', 'documents', 'rag (semantic and full-text doc search)'."

## Use case

AI agents call docs to retrieve information from Frisian MCP (Django) 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 Frisian MCP (Django):

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

## Other tools on Frisian MCP (Django) (3)

- `demo` — Execute — https://policylayer.com/tools/com-frisian-mcp-django/demo.md
- `install` — Read — https://policylayer.com/tools/com-frisian-mcp-django/install.md
- `troubleshooting` — Read — https://policylayer.com/tools/com-frisian-mcp-django/troubleshooting.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-frisian-mcp-django · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-frisian-mcp-django