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.
This record as markdown: /tools/com-frisian-mcp-django/troubleshooting.md
What troubleshooting does on Frisian MCP (Django)
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | — | Operation to perform. Omit or use 'help' to list all available actions and their required parameters. |
params | object | — | Action-specific parameters. nautobot: (no params); netbox: (no params); paperless: (no params); edx: (no params). |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs troubleshooting safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frisian MCP (Django), and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For troubleshooting, this is the rule to start with:
troubleshooting is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Frisian MCP (Django), apply this rule, and every troubleshooting call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Frisian MCP (Django) MCP Server, which means it retrieves data without modifying state.
troubleshooting accepts 2 parameters: action, params. The full parameter table on this page comes from the server's own tool schema.
Register the Frisian MCP (Django) MCP server in PolicyLayer and add a rule for troubleshooting: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Frisian MCP (Django). Nothing to install.
troubleshooting is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the troubleshooting rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for troubleshooting. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
troubleshooting is provided by the Frisian MCP (Django) MCP server (https://mcp.frisian-mcp.com/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Frisian MCP (Django), and thousands of servers like it.
This server
Across the catalogue