machine_roles

SERVERYaver SOURCEyaver-cli

Medium RISK CLASS

Category Write

Parameters 100 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/machine-roles.md

WHAT IT DOES

What machine_roles does on Yaver

AI agents use machine_roles to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.

Parameter	Type	Required	Description
`action`	string	—	get current split, set runner/render, or clear back to single-box.
`render`	string	—	Renderer selector. Defaults to runner.
`runner`	string	—	Runner selector: deviceId, unique prefix, name, or alias.
`autoPush`	string	—
`workspace`	string	—
`projectName`	string	—
`renderDeviceId`	string	—	Renderer device selector.
`runnerDeviceId`	string	—	Runner device selector.
`secondaryRender`	string	—
`secondaryRunner`	string	—

Parameters from the server's own tool schema.

RISK

Why machine_roles is rated Medium

The tool both reads and writes configuration — specifically it writes/clears machine role settings (primary AI runner and renderer) that affect routing across Claude Code, Codex, task chats, and MCP clients. Since it can modify shared configuration, Write is the appropriate category. Misuse could redirect AI execution to unintended machines, but the effect is reversible (can be reset), making severity medium.

From the tool's definition 'set, or clear the user's primary AI runner and primary renderer. Writes the same machineRolesForProject setting'

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs machine_roles 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 machine_roles, this is the rule to start with:

machine_roles Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "machine_roles": {
      "limits": [
        {
          "counter": "machine_roles_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every machine_roles call is checked against it from then on.

FAQ

Questions about machine_roles

What does the machine_roles tool do? +

Read, set, or clear the user's primary AI runner and primary renderer. Writes the same machineRolesForProject setting used by web/mobile, so Claude Code, Codex, task chats, and MCP clients share one runner/render routing source. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does machine_roles accept? +

machine_roles accepts 10 parameters: action, render, runner, autoPush, workspace, projectName, renderDeviceId, runnerDeviceId, secondaryRender, secondaryRunner. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on machine_roles? +

Register the Yaver MCP server in PolicyLayer and add a rule for machine_roles: 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.

What risk level is machine_roles? +

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

Can I rate-limit machine_roles? +

Yes. Add a rate_limit block to the machine_roles 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 machine_roles completely? +

Set action: deny in the PolicyLayer policy for machine_roles. 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 machine_roles? +

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

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →