New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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...

SERVEREasyBits SOURCE@easybits.cloud/mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

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

Questions about set_machine_runspec

What does the set_machine_runspec tool do? +

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.

How do I enforce a policy on set_machine_runspec? +

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.

What risk level is set_machine_runspec? +

set_machine_runspec is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_machine_runspec? +

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.

How do I block set_machine_runspec completely? +

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.

What MCP server provides set_machine_runspec? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of EasyBits's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.