service_status

Check status of a system service (systemd on Linux, brew services on macOS).

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/service-status.md

WHAT IT DOES

What service_status does on Yaver

AI agents call service_status to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`name`	string	Yes	Service name (e.g. nginx, postgresql, docker)

Parameters from the server's own tool schema.

RISK

Why service_status is rated Low

The tool performs a status check (a read operation) on system services. It queries the state of systemd or brew services but does not start, stop, restart, or modify any services. This is informational only with no side effects, placing it firmly in the Read category.

From the tool's definition Tool description: 'Check status of a system service' — this is a read-only query operation that retrieves service state information without modifying or executing any services.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

service_status Allowed

service_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "service_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about service_status

What does the service_status tool do? +

Check status of a system service (systemd on Linux, brew services on macOS). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does service_status accept? +

service_status accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on service_status? +

Register the Yaver MCP server in PolicyLayer and add a rule for service_status: 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_status? +

service_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit service_status? +

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

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

service_status 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

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →