This record as markdown: /tools/io-github-kivanccakmak-yaver/remote-exec.md
What remote_exec does on Yaver
AI agents invoke remote_exec 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 |
|---|---|---|---|
command | string | Yes | |
machine_id | string | Yes |
Parameters from the server's own tool schema.
Why remote_exec is rated High
This tool permits execution of shell commands on remote machines, which is inherently dangerous if misused by an AI agent. The agent could run destructive commands, install malware, exfiltrate data, or compromise remote infrastructure. This is a textbook Execute risk with critical severity due to the unrestricted nature of command execution and potential for lateral movement or system compromise.
From the tool's definition Tool name 'remote_exec' with description 'Execute a command on a remote machine' directly indicates execution of arbitrary commands on remote systems.
Attacks that exploit this kind of access
The rule that runs remote_exec 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_exec, this is the rule to start with:
remote_exec 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_exec call is checked against it from then on.
Questions about remote_exec
Execute a command on a remote machine. 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_exec accepts 2 parameters: command, machine_id. Required: command, machine_id. 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_exec: 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_exec 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_exec 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_exec. 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_exec 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