service_stop

Stop a running service by name (e.g.

SERVERTruenas SOURCEspranab/truenas-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/spranab-truenas-mcp/service-stop.md

WHAT IT DOES

What service_stop does on Truenas

AI agents invoke service_stop to trigger actions in Truenas. 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.

RISK

Why service_stop is rated High

Stopping a running service is an execute action that triggers external operations (stopping system services) whose effects depend on which service is specified as an argument. While not destructive or financial, it can disrupt system operations and dependent services. The high severity reflects that stopping critical services could cause significant system downtime or failure.

From the tool's definition Tool name 'service_stop' and description 'Stop a running service by name' indicates the tool executes a command to terminate a system service.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs service_stop safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Truenas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For service_stop, this is the rule to start with:

service_stop Rate-limited

service_stop 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_stop": {
      "limits": [
        {
          "counter": "service_stop_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 Truenas, apply this rule, and every service_stop call is checked against it from then on.

FAQ

Questions about service_stop

What does the service_stop tool do? +

Stop a running service by name (e.g. It is categorised as a Execute tool in the Truenas MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on service_stop? +

Register the Truenas MCP server in PolicyLayer and add a rule for service_stop: 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 Truenas. Nothing to install.

What risk level is service_stop? +

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

Can I rate-limit service_stop? +

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

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

service_stop is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Truenas, and thousands of servers like it.

This server

All 279 Truenas tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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