docs_config

Point the docs site at a markdown folder, set title / theme / logo.

SERVERYaver SOURCEyaver-cli

Medium RISK CLASS

Category Write

Parameters 40 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/docs-config.md

WHAT IT DOES

What docs_config does on Yaver

AI agents use docs_config to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.

Parameter	Type	Required
`path`	string	—
`theme`	string	—
`title`	string	—
`logoUrl`	string	—

Parameters from the server's own tool schema.

RISK

Why docs_config is rated Medium

This tool modifies configuration settings for a documentation site (folder path, title, theme, logo). These are reversible changes that update/write configuration data. No code execution, deletion, or financial action is involved.

From the tool's definition Point the docs site at a markdown folder, set title / theme / logo

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs docs_config safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docs_config, this is the rule to start with:

docs_config Rate-limited

docs_config stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "docs_config": {
      "limits": [
        {
          "counter": "docs_config_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every docs_config call is checked against it from then on.

FAQ

Questions about docs_config

What does the docs_config tool do? +

Point the docs site at a markdown folder, set title / theme / logo. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does docs_config accept? +

docs_config accepts 4 parameters: path, theme, title, logoUrl. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on docs_config? +

Register the Yaver MCP server in PolicyLayer and add a rule for docs_config: 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 Yaver. Nothing to install.

What risk level is docs_config? +

docs_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit docs_config? +

Yes. Add a rate_limit block to the docs_config 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.

How do I block docs_config completely? +

Set action: deny in the PolicyLayer policy for docs_config. 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.

What MCP server provides docs_config? +

docs_config is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

generate_docs on MCP Server PR Pilot → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →