config_set

Set a Yaver configuration value. Keys: auto-start, auto-update, headless-keep-awake, require-private-recovery.

SERVERYaver SOURCEyaver-cli

Medium RISK CLASS

Category Write

Parameters 22 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/config-set.md

WHAT IT DOES

What config_set does on Yaver

AI agents use config_set 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	Description
`key`	string	Yes	Config key (auto-start, auto-update, headless-keep-awake, require-private-recovery)
`value`	string	Yes	Config value

Parameters from the server's own tool schema.

RISK

Why config_set is rated Medium

This tool creates or modifies configuration settings in a reversible manner. While it affects system behavior (auto-start, auto-update, keep-awake states, and recovery policies), these changes are not permanent deletions and can be reverted by setting values again.

From the tool's definition Tool description states 'Set a Yaver configuration value' with keys including 'auto-start', 'auto-update', 'headless-keep-awake', 'require-private-recovery'. The verb 'Set' and the act of modifying configuration values indicates data modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs config_set 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 config_set, this is the rule to start with:

config_set Rate-limited

config_set 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": {
    "config_set": {
      "limits": [
        {
          "counter": "config_set_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 config_set call is checked against it from then on.

FAQ

Questions about config_set

What does the config_set tool do? +

Set a Yaver configuration value. Keys: auto-start, auto-update, headless-keep-awake, require-private-recovery. 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 config_set accept? +

config_set accepts 2 parameters: key, value. Required: key, value. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on config_set? +

Register the Yaver MCP server in PolicyLayer and add a rule for config_set: 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 config_set? +

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

Can I rate-limit config_set? +

Yes. Add a rate_limit block to the config_set 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 config_set completely? +

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

config_set 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

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

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