service_status
Return systemd active/enabled states for services.
This record as markdown: /tools/mcp-control-plane/service-status.md
What service_status does on Mcp Control Plane
AI agents call service_status to retrieve information from Mcp Control Plane without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why service_status is rated Low
This tool queries systemd service states (active/enabled status) and returns this information. It has no side effects, does not execute commands, create, modify, or delete data. It is a pure information retrieval operation, fitting the Read category. Severity is low because knowing service states poses minimal security risk unless combined with other tools for malicious orchestration.
From the tool's definition Tool name 'service_status' and description 'Return systemd active/enabled states for services' indicate a query operation that retrieves system state information without modification.
Attacks that exploit this kind of access
The rule that runs service_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every service_status call is checked against it from then on.
Questions about service_status
Return systemd active/enabled states for services. It is categorised as a Read tool in the Mcp Control Plane MCP Server, which means it retrieves data without modifying state.
Register the Mcp Control Plane 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 Mcp Control Plane. Nothing to install.
service_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
service_status is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
This server
Across the catalogue