system_general_update
Update general system configuration. All fields are optional — only provide the ones you want to change. Changes to UI ports may require reconnecting on the new port.
This record as markdown: /tools/nasbridge/system-general-update.md
What system_general_update does on Nasbridge
AI agents use system_general_update 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_general_update is rated Medium
This tool creates or modifies system configuration data reversibly. While it affects critical system settings like UI ports, the changes are not irreversible deletions/destructions, nor do they execute arbitrary code or trigger financial transactions.
From the tool's definition Tool name 'system_general_update' explicitly states 'Update' operation on 'general system configuration'. Description confirms it modifies settings ('only provide the ones you want to change') and warns of side effects ('may require reconnecting on the new…
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs system_general_update 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_general_update, this is the rule to start with:
system_general_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every system_general_update call is checked against it from then on.
Questions about system_general_update
Update general system configuration. All fields are optional — only provide the ones you want to change. Changes to UI ports may require reconnecting on the new port. 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_general_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 Nasbridge. Nothing to install.
system_general_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 system_general_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 system_general_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.
system_general_update 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