List all system services with their current status (running/stopped) and whether they are enabled at boot. Useful for an overview of all available services.
AI agents call service_list to retrieve information from Truenas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that queries and returns service status information. It has no side effects—it does not create, modify, delete, or execute any system changes. The blast radius of misuse is minimal since an agent can only view information, not alter system state. Low severity is appropriate for reconnaissance-only access.
From the tool's definition Tool name 'service_list' and description 'List all system services with their current status (running/stopped) and whether they are enabled at boot' indicate a query operation that retrieves service status information without modifying, deleting, or executing…
Documented attack patterns abuse exactly the kind of access service_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Truenas, and nothing reaches the server without passing your rules. This is the rule we recommend for service_list:
{
"version": "1",
"default": "deny",
"tools": {
"service_list": {}
}
}service_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all system services with their current status (running/stopped) and whether they are enabled at boot. Useful for an overview of all available services. It is categorised as a Read tool in the Truenas MCP Server, which means it retrieves data without modifying state.
Register the Truenas MCP server in PolicyLayer and add a rule for service_list: 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.
service_list 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_list 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_list. 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_list 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.
Start from Truenas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
279 Truenas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.