set_machine_runspec
Declare HOW to build and run the app on a machine: appDir (required), plus buildCommand/startCommand or a systemd unit, port, and dataPaths (what the daily backup captures). Required before deploy_machine. Merges with the existing runspec. Do NOT put secrets in env — it is stored and baked into e...
This record as markdown: /tools/cloud-easybits-easybits/set-machine-runspec.md
What set_machine_runspec does on EasyBits
AI agents use set_machine_runspec to create or update resources in EasyBits, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EasyBits environment.
Why set_machine_runspec is rated Medium
Modifies machine configuration; affects build/runtime behavior but is reversible and precedes deployment.
From the tool's definition Declare HOW to build and run the app on a machine; merges with existing runspec.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs set_machine_runspec safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_machine_runspec, this is the rule to start with:
set_machine_runspec stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every set_machine_runspec call is checked against it from then on.
Questions about set_machine_runspec
Declare HOW to build and run the app on a machine: appDir (required), plus buildCommand/startCommand or a systemd unit, port, and dataPaths (what the daily backup captures). Required before deploy_machine. Merges with the existing runspec. Do NOT put secrets in env — it is stored and baked into every release tarball; use the vault instead. It is categorised as a Write tool in the EasyBits MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EasyBits MCP server in PolicyLayer and add a rule for set_machine_runspec: 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 EasyBits. Nothing to install.
set_machine_runspec is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_machine_runspec 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 set_machine_runspec. 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.
set_machine_runspec is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
This server
Across the catalogue