Update an existing network interface. All fields are optional — only provide the ones you want to change. Network changes are staged until committed with network_commit_changes.
AI agents use network_interface_update to create or update resources in Truenas — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Truenas environment.
The tool updates network interface configuration, which is a write operation that modifies system state. It's reversible (changes are staged until committed), so it falls under Write rather than Destructive. The severity is high because misconfigured network interfaces can severely impact system connectivity and accessibility, creating a significant blast radius if an AI agent makes unintended changes.
From the tool's definition Tool name: 'network_interface_update'. Description: 'Update an existing network interface. All fields are optional — only provide the ones you want to change.' This modifies network configuration reversibly until committed.
Documented attack patterns abuse exactly the kind of access network_interface_update 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_interface_update:
{
"version": "1",
"default": "deny",
"tools": {
"network_interface_update": {
"limits": [
{
"counter": "network_interface_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}network_interface_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update an existing network interface. All fields are optional — only provide the ones you want to change. Network changes are staged until committed with network_commit_changes. It is categorised as a Write tool in the Truenas MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Truenas MCP server in PolicyLayer and add a rule for network_interface_update: 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_interface_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the network_interface_update 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_interface_update. 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_interface_update 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.