Get details of a specific service by its numeric ID, including its running state and boot-time enable status.
AI agents call service_get 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 tool retrieves service information (running state and boot settings) without creating, modifying, or deleting anything. It is a pure query operation that has no side effects on the TrueNAS system. The low severity reflects minimal risk even if an agent queries service details, as this provides only informational output.
From the tool's definition Tool description states 'Get details of a specific service by its numeric ID, including its running state and boot-time enable status.' The verb 'Get' and the context of retrieving service metadata indicate a read-only operation with no data modification.
Documented attack patterns abuse exactly the kind of access service_get 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_get:
{
"version": "1",
"default": "deny",
"tools": {
"service_get": {}
}
} service_get 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.
Get details of a specific service by its numeric ID, including its running state and boot-time enable status. 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_get: 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_get 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_get 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_get. 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_get 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.