machine_onboarding_status
Show whether OpenAI, GitHub, and GitLab are configured on this machine or on one or more owned Yaver machines. Reports OpenAI API key readiness plus Git clone and CI/deploy token state.
This record as markdown: /tools/io-github-kivanccakmak-yaver/machine-onboarding-status.md
What machine_onboarding_status does on Yaver
AI agents call machine_onboarding_status 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
device_id | string | — | Optional remote device ID |
device_ids | array | — | Optional list of owned remote device IDs |
Parameters from the server's own tool schema.
Why machine_onboarding_status is rated Low
This tool retrieves and displays the state of machine configurations (OpenAI, GitHub, GitLab credentials and readiness) without altering them. It is a diagnostic/status check that produces no side effects. Even though it touches sensitive information (API keys, tokens), the tool itself does not create, modify, execute, or delete anything—it only reads and reports existing state.
From the tool's definition Tool description states it 'shows' and 'reports' configuration status—purely informational queries with no modification or execution.
Attacks that exploit this kind of access
The rule that runs machine_onboarding_status 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 machine_onboarding_status, this is the rule to start with:
machine_onboarding_status 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 Yaver, apply this rule, and every machine_onboarding_status call is checked against it from then on.
Questions about machine_onboarding_status
Show whether OpenAI, GitHub, and GitLab are configured on this machine or on one or more owned Yaver machines. Reports OpenAI API key readiness plus Git clone and CI/deploy token state. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
machine_onboarding_status accepts 2 parameters: device_id, device_ids. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for machine_onboarding_status: 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.
machine_onboarding_status 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 machine_onboarding_status 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 machine_onboarding_status. 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.
machine_onboarding_status 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.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue