system_config_upload
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.
This record as markdown: /tools/nasbridge/system-config-upload.md
What system_config_upload does on Nasbridge
AI agents use system_config_upload to create or update resources in Nasbridge, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nasbridge environment.
Why system_config_upload is rated Medium
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
Attacks that exploit this kind of access
The rule that runs system_config_upload safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For system_config_upload, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every system_config_upload call is checked against it from then on.
Questions about system_config_upload
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 Nasbridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nasbridge 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 Nasbridge. 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 Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue