system_service_control · Infra Ops MCP: Risk & Policy

WHAT IT DOES

What system_service_control does on Infra Ops

AI agents invoke system_service_control to trigger actions in Infra Ops. 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.

WHY IT NEEDS A POLICY

Why system_service_control needs a policy

This tool executes external operations (service lifecycle management) whose effects depend on which service is targeted. While it requires confirmation, the ability to stop/start critical system services can disrupt infrastructure, cause downtime, or interfere with security controls.

From the tool's definition Tool description explicitly states it can 'Start, stop, or restart a system service' using OS-level service management commands (sc, systemctl, launchctl). These operations trigger external system processes and state changes.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

system_service_control Rate-limited

system_service_control 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": {
    "system_service_control": {
      "limits": [
        {
          "counter": "system_service_control_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Infra Ops, so you can run agents against it safely.

FAQ

Questions about system_service_control

What does the system_service_control tool do? +

Start, stop, or restart a system service. Requires confirmation. Uses sc on Windows, systemctl on Linux, launchctl on macOS. It is categorised as a Execute tool in the Infra Ops MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on system_service_control? +

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

What risk level is system_service_control? +

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

Can I rate-limit system_service_control? +

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

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

system_service_control is provided by the Infra Ops MCP server (skyvanguard/infra-ops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.