infra_service_action
Start, stop, restart, or inspect a managed service. Scope can be dev (.yaver/services.yaml) or system (systemd/brew services).
This record as markdown: /tools/io-github-kivanccakmak-yaver/infra-service-action.md
What infra_service_action does on Yaver
AI agents invoke infra_service_action 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 |
|---|---|---|---|
name | string | Yes | Service name |
scope | string | Yes | dev or system |
action | string | Yes | start, stop, restart, or status |
Parameters from the server's own tool schema.
Why infra_service_action is rated High
This tool executes control operations over services whose effects depend on which service is targeted. While not destructive (services can be restarted), and not Write (it doesn't create/modify persistent data), it directly triggers external operations (systemd/brew commands) that alter runtime state. Misuse could stop critical services, disrupt development workflows, or affect system stability.
From the tool's definition The tool can 'start, stop, restart' services and 'inspect' them. Starting/stopping/restarting services are Execute-class actions that trigger external operations with real effects on system state.
Attacks that exploit this kind of access
The rule that runs infra_service_action 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 infra_service_action, this is the rule to start with:
infra_service_action 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 infra_service_action call is checked against it from then on.
Questions about infra_service_action
Start, stop, restart, or inspect a managed service. Scope can be dev (.yaver/services.yaml) or system (systemd/brew services). 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.
infra_service_action accepts 3 parameters: name, scope, action. Required: name, scope, action. 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 infra_service_action: 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.
infra_service_action 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 infra_service_action 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 infra_service_action. 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.
infra_service_action 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