Get TrueNAS system information including hostname, version, uptime, CPU, memory, and hardware details. Use this to understand the system you are managing.
AI agents call system_info 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 only retrieves and queries system metadata about a TrueNAS instance. It has no side effects, creates no changes, executes no code, and poses minimal security risk. It is a typical Read operation used for monitoring and understanding system state.
From the tool's definition Tool name is 'system_info' and description explicitly states it 'Get[s] TrueNAS system information including hostname, version, uptime, CPU, memory, and hardware details.' This is purely informational retrieval with no modification, deletion, execution, or…
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access system_info 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 system_info:
{
"version": "1",
"default": "deny",
"tools": {
"system_info": {}
}
}system_info 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 TrueNAS system information including hostname, version, uptime, CPU, memory, and hardware details. Use this to understand the system you are managing. 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 system_info: 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.
system_info 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 system_info 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 system_info. 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.
system_info 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.