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 ...
This record as markdown: /tools/com-frisian-mcp-django/docs.md
What docs does on Frisian MCP (Django)
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.
| 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. about: {version}; getting_started: {version}; integrations: {version}; security: {version}; demo: {surface}; documents: {sub_action, |
Parameters from the server's own tool schema.
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 definition Tool description states it provides documentation and guides: 'about', 'getting_started', 'integrations', 'security', 'demo', 'documents', 'rag (semantic and full-text doc search)'.
Attacks that exploit this kind of access
The rule that runs docs 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 docs, this is the rule to start with:
docs 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 docs call is checked against it from then on.
Questions about 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). It is categorised as a Read tool in the Frisian MCP (Django) MCP Server, which means it retrieves data without modifying state.
docs 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 docs: 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.
docs 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 docs 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 docs. 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.
docs 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