Get TrueNAS system information: version, uptime, CPU, RAM, boot time.
AI agents call system_info to retrieve information from Truenas Ws without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward information-retrieval operation. It queries system metadata and reports it back without side effects, state changes, or resource consumption beyond simple reads. The low severity reflects that misuse would only expose system details, not compromise infrastructure or data.
From the tool's definition Tool retrieves system information (version, uptime, CPU, RAM, boot time) with no indication of modification, deletion, or execution capabilities. The description explicitly lists only 'Get' operations.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Get TrueNAS system information: version, uptime, CPU, RAM, boot time. It is categorised as a Read tool in the Truenas Ws MCP Server, which means it retrieves data without modifying state.
Register the Truenas Ws 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 Ws. 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 Ws MCP server (thoriphes/truenas-ws-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →