sandbox_quickstart
One-step containerization setup for Yaver owner tasks. Persists the setting and optionally starts building the yaver-sandbox image.
This record as markdown: /tools/io-github-kivanccakmak-yaver/sandbox-quickstart.md
What sandbox_quickstart does on Yaver
AI agents invoke sandbox_quickstart 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 |
|---|---|---|---|
mode | string | — | Quickstart mode; only 'host' is supported |
build_image | boolean | — | Start building the sandbox image immediately (default true) |
Parameters from the server's own tool schema.
Why sandbox_quickstart is rated High
Triggers container image build and persists configuration, executing external operations.
From the tool's definition containerization setup, starts building the yaver-sandbox image
Attacks that exploit this kind of access
The rule that runs sandbox_quickstart 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 sandbox_quickstart, this is the rule to start with:
sandbox_quickstart 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 sandbox_quickstart call is checked against it from then on.
Questions about sandbox_quickstart
One-step containerization setup for Yaver owner tasks. Persists the setting and optionally starts building the yaver-sandbox image. 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.
sandbox_quickstart accepts 2 parameters: mode, build_image. 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 sandbox_quickstart: 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.
sandbox_quickstart 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 sandbox_quickstart 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 sandbox_quickstart. 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.
sandbox_quickstart 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