yaver_self_host_onboarding

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 50 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/yaver-self-host-onboarding.md

WHAT IT DOES

What yaver_self_host_onboarding does on Yaver

AI agents invoke yaver_self_host_onboarding to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`runner`	string	—	Preferred coding runner: codex, claude-code, opencode
`repo_query`	string	—	Optional app/repo name the user wants to use
`git_provider`	string	—	Provider for optional Device Flow
`start_git_oauth`	boolean	—	Start GitHub/GitLab Device Flow now; user approves in browser
`include_cloud_cta`	boolean	—	Include the managed-cloud upgrade path in the response

Parameters from the server's own tool schema.

RISK

Why yaver_self_host_onboarding is rated High

This is an Execute tool because it triggers external operations whose effects depend on arguments, specifically: starting OAuth Device Flows, configuring CI/CD runners, and initiating server processes.

From the tool's definition The tool 'can start GitHub/GitLab Device Flow' and handles 'GitHub/GitLab credentials' setup, 'runner setup', and 'serve' operations. It executes a 'guided MCP flow' that initiates OAuth flows and configures system services.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

yaver_self_host_onboarding Rate-limited

yaver_self_host_onboarding stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "yaver_self_host_onboarding": {
      "limits": [
        {
          "counter": "yaver_self_host_onboarding_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about yaver_self_host_onboarding

What does the yaver_self_host_onboarding tool do? +

High-level guided MCP flow for setting up Yaver on the user's own machine/VPS. Returns normie-friendly next steps for auth, serve, phone pairing, repo selection, runner setup, GitHub/GitLab credentials, and optional cloud upgrade. Can start GitHub/GitLab Device Flow when start_git_oauth=true. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does yaver_self_host_onboarding accept? +

yaver_self_host_onboarding accepts 5 parameters: runner, repo_query, git_provider, start_git_oauth, include_cloud_cta. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on yaver_self_host_onboarding? +

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

yaver_self_host_onboarding is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit yaver_self_host_onboarding? +

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

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

yaver_self_host_onboarding 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →