machine_onboarding_remove

Remove GitHub/GitLab onboarding from the local machine or from one or more owned Yaver machines. Can remove clone credentials, CI/deploy vault tokens, or both.

SERVERYaver SOURCEyaver-cli

Critical RISK CLASS

Category Destructive

Parameters 60 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/machine-onboarding-remove.md

WHAT IT DOES

What machine_onboarding_remove does on Yaver

AI agents call machine_onboarding_remove to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`device_id`	string	—	Optional remote device ID
`providers`	array	—	Providers to remove
`device_ids`	array	—	Optional list of owned remote device IDs
`gitlab_host`	string	—	Optional specific GitLab host to clear
`remove_clone`	boolean	—	Remove clone/pull credentials and provider config (default true)
`remove_ci_token`	boolean	—	Remove CI/deploy vault token (default true)

Parameters from the server's own tool schema.

RISK

Why machine_onboarding_remove is rated Critical

The tool irreversibly deletes stored credentials and authentication tokens. While not deleting user data per se, removing vault tokens and clone credentials are destructive actions that cannot be easily undone and will break CI/CD pipelines and repository access. This has a high blast radius if invoked incorrectly on production machines.

From the tool's definition Tool performs 'Remove' operations on GitHub/GitLab onboarding, including removal of 'clone credentials' and 'CI/deploy vault tokens' from machines.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

machine_onboarding_remove Hidden

machine_onboarding_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "machine_onboarding_remove"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about machine_onboarding_remove

What does the machine_onboarding_remove tool do? +

Remove GitHub/GitLab onboarding from the local machine or from one or more owned Yaver machines. Can remove clone credentials, CI/deploy vault tokens, or both. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does machine_onboarding_remove accept? +

machine_onboarding_remove accepts 6 parameters: device_id, providers, device_ids, gitlab_host, remove_clone, remove_ci_token. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on machine_onboarding_remove? +

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

machine_onboarding_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit machine_onboarding_remove? +

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

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

machine_onboarding_remove 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 → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →