systemctl
Manage systemd services (status, start, stop, restart, enable, disable, list, failed, timers).
This record as markdown: /tools/io-github-kivanccakmak-yaver/systemctl.md
What systemctl does on Yaver
AI agents invoke systemctl 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 |
|---|---|---|---|
unit | string | — | |
action | string | Yes | status, start, stop, restart, enable, disable, list, failed, timers |
Parameters from the server's own tool schema.
Why systemctl is rated High
This tool executes system-level commands via systemctl to manage daemon services. While not destructive in the sense of deleting data, it can stop critical services, restart processes, or enable/disable functionality—actions with significant operational impact. The blast radius is high: misconfiguration or malicious arguments could disable services, crash applications, or cause system-wide outages.
From the tool's definition Tool performs service management operations including start, stop, restart, enable, disable—these are control-plane actions that trigger external systemd operations whose effects depend on arguments (which service is targeted, which action is invoked).
Attacks that exploit this kind of access
The rule that runs systemctl 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 systemctl, this is the rule to start with:
systemctl 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 systemctl call is checked against it from then on.
Questions about systemctl
Manage systemd services (status, start, stop, restart, enable, disable, list, failed, timers). 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.
systemctl accepts 2 parameters: unit, action. Required: 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 systemctl: 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.
systemctl 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 systemctl 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 systemctl. 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.
systemctl 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