Get the global network configuration including hostname, domain, gateways, nameservers, and proxy settings.
AI agents call network_config 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 and queries network configuration information without any side effects or state changes. It is a read-only operation that returns existing system configuration data. The low severity reflects minimal risk from exposure—understanding the network configuration could inform further attacks but does not directly enable them or cause damage. No confirmation mechanism is needed for a read operation.
From the tool's definition Tool name 'network_config' combined with description 'Get the global network configuration' indicates retrieval of configuration data.
Documented attack patterns abuse exactly the kind of access network_config 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_config:
{
"version": "1",
"default": "deny",
"tools": {
"network_config": {}
}
}network_config 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 the global network configuration including hostname, domain, gateways, nameservers, and proxy settings. 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_config: 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_config 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_config 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_config. 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_config 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.