# troubleshooting

Troubleshooting guides for frisian-mcp integrations (Django framework tier). Actions: nautobot, netbox, paperless, edx. Each action returns diagnostic guides and relevant files for that integration. Pass query for semantic search within the section.

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

## Facts

- Tool: `troubleshooting`
- 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. nautobot: (no params); netbox: (no params); paperless: (no params); edx: (no params). |

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

## Why troubleshooting is rated Low

This tool retrieves and queries troubleshooting documentation and diagnostic information. It has no side effects beyond reading data. The 'pass query for semantic search' confirms a read/query pattern. Although it references external integrations (nautobot, netbox, etc.), it only returns guides and files about those systems, not commands or operations that execute against them.

From the tool's own definition: "The tool returns 'diagnostic guides and relevant files' and supports 'semantic search within the section'. No modification, deletion, execution of external systems, or financial operations are described."

## Use case

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

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

- `demo` — Execute — https://policylayer.com/tools/com-frisian-mcp-django/demo.md
- `docs` — Read — https://policylayer.com/tools/com-frisian-mcp-django/docs.md
- `install` — Read — https://policylayer.com/tools/com-frisian-mcp-django/install.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