remote_setup
First-time setup of a remote dev machine (installs Docker, Node.js, Git, Yaver agent).
This record as markdown: /tools/io-github-kivanccakmak-yaver/remote-setup.md
What remote_setup does on Yaver
AI agents invoke remote_setup 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 |
|---|---|---|---|
host | string | Yes | IP or hostname |
user | string | — | SSH user (default: root) |
Parameters from the server's own tool schema.
Why remote_setup is rated High
This tool runs installation commands on a remote machine, installing software packages (Docker, Node.js, Git, Yaver agent). This constitutes executing operations on an external system with significant side effects. Misuse could install malicious software or misconfigure a remote machine, hence high severity.
From the tool's definition 'First-time setup of a remote dev machine (installs Docker, Node.js, Git, Yaver agent)'
Risk signalsAccepts URL/endpoint input (host)
Attacks that exploit this kind of access
The rule that runs remote_setup 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 remote_setup, this is the rule to start with:
remote_setup 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every remote_setup call is checked against it from then on.
Questions about remote_setup
First-time setup of a remote dev machine (installs Docker, Node.js, Git, Yaver agent). 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.
remote_setup accepts 2 parameters: host, user. Required: host. 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 remote_setup: 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.
remote_setup is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the remote_setup 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 remote_setup. 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.
remote_setup 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.
Across the catalogue