Start a service by name (e.g.
AI agents invoke service_start 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.
Starting a service is an Execute action because it triggers system-level operations with real-world side effects. The severity is high because misuse could start critical services unexpectedly (e.g., malware distribution services, resource-intensive processes, or services that expose security vulnerabilities), affecting system stability and security.
From the tool's definition Tool name 'service_start' and description indicate it starts a service by name. This is an executable action that triggers external system operations (service initialization) whose effects depend on which service is specified as an argument.
Documented attack patterns abuse exactly the kind of access service_start 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_start:
{
"version": "1",
"default": "deny",
"tools": {
"service_start": {
"limits": [
{
"counter": "service_start_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}service_start 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.
Free to start. No card required.
Start a 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.
Register the Truenas MCP server in PolicyLayer and add a rule for service_start: 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_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the service_start 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_start. 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_start 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.