Get IPMI chassis information if IPMI is available on this system. First checks whether IPMI hardware is present.
AI agents call network_ipmi_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 retrieves system hardware information (IPMI status and chassis details) without any side effects. It reads existing data and performs checks only. There is no capability to modify, delete, execute code, or commit financial transactions. The blast radius of misuse is minimal since an AI agent could only obtain information about the system's IPMI hardware status.
From the tool's definition Tool performs 'Get IPMI chassis information' and 'checks whether IPMI hardware is present' - purely informational operations with no data modification, deletion, or system state changes.
Documented attack patterns abuse exactly the kind of access network_ipmi_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 network_ipmi_info:
{
"version": "1",
"default": "deny",
"tools": {
"network_ipmi_info": {}
}
}network_ipmi_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 IPMI chassis information if IPMI is available on this system. First checks whether IPMI hardware is present. 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 network_ipmi_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.
network_ipmi_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 network_ipmi_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 network_ipmi_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.
network_ipmi_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.