service_action

Start, stop, restart, enable, or disable a system service.

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 22 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/service-action.md

WHAT IT DOES

What service_action does on Yaver

AI agents invoke 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
`action`	string	Yes	start, stop, restart, enable, disable

Parameters from the server's own tool schema.

RISK

Why service_action is rated High

This tool executes commands that control system services—a form of code execution with side effects. While not destructive in the permanent data-loss sense, restarting or disabling critical services can disrupt operations, cause downtime, or indirectly impact data availability. The tool's effect depends entirely on which service argument an AI agent targets.

From the tool's definition Tool description states it can 'Start, stop, restart, enable, or disable a system service.' These are external operations that trigger immediate effects on system state and behavior.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

service_action Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "service_action": {
      "limits": [
        {
          "counter": "service_action_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about service_action

What does the service_action tool do? +

Start, stop, restart, enable, or disable a system service. 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.

What parameters does service_action accept? +

service_action accepts 2 parameters: name, action. Required: name, action. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on service_action? +

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

What risk level is service_action? +

service_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit service_action? +

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

How do I block service_action completely? +

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

What MCP server provides service_action? +

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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → High-risk tools on this server →

Across the catalogue

qt_trigger_action on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →