Get network configuration: DNS servers, gateway, hostname.
AI agents call get_network_config 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 tool retrieves network configuration data (DNS servers, gateway, hostname) without creating, modifying, deleting, or executing any operations. It is a simple query operation with no impact on system state or data integrity. Low severity because the information retrieved is typically non-sensitive infrastructure metadata.
From the tool's definition Tool name 'get_network_config' and description 'Get network configuration: DNS servers, gateway, hostname' indicates a read-only retrieval of existing network settings with no modification or side effects.
Attacks that exploit this kind of access
Get network configuration: DNS servers, gateway, hostname. 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 get_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 Ws. Nothing to install.
get_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 get_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 get_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.
get_network_config 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 →