Upload a system configuration file to restore settings. Note: this endpoint typically expects a multipart file upload which may not be fully supported via the REST JSON client. Use the TrueNAS web UI for reliable config restores.
AI agents use system_config_upload 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.
This tool uploads and restores system configuration files, which modifies system settings reversibly (configurations can be changed again). While restoration of configs is a Write operation rather than Destructive (since configs are not permanently deleted—they can be reconfigured), the blast radius is high because incorrect or malicious configurations could severely compromise system security, availability, or…
From the tool's definition Tool name 'system_config_upload' and description 'Upload a system configuration file to restore settings' indicates modification of system configuration state.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access system_config_upload 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 system_config_upload:
{
"version": "1",
"default": "deny",
"tools": {
"system_config_upload": {
"limits": [
{
"counter": "system_config_upload_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}system_config_upload 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.
Upload a system configuration file to restore settings. Note: this endpoint typically expects a multipart file upload which may not be fully supported via the REST JSON client. Use the TrueNAS web UI for reliable config restores. 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 system_config_upload: 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.
system_config_upload 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 system_config_upload 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_config_upload. 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_config_upload 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.