yaver_onboard

Drive the first-run onboarding flow for a fresh Yaver install. Returns the ordered checklist of steps the user still needs to complete (auth, bootstrap secret, tunnel, runner, etc.) based on the current config state. Call this before doing any setup work so you know where to start.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What yaver_onboard does on Yaver

AI agents call yaver_onboard to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why yaver_onboard is rated Low

The tool reads and inspects the current configuration state to determine which onboarding steps remain. It returns a checklist but does not perform any setup actions itself — it is a diagnostic/status query tool. The phrase 'before doing any setup work' confirms it is read-only preparation, not execution.

From the tool's definition Returns the ordered checklist of steps the user still needs to complete... based on the current config state. Call this before doing any setup work so you know where to start.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

yaver_onboard Allowed

yaver_onboard is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "yaver_onboard": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about yaver_onboard

What does the yaver_onboard tool do? +

How do I enforce a policy on yaver_onboard? +

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

yaver_onboard is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit yaver_onboard? +

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

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

yaver_onboard 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

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →