network_config
Get the global network configuration including hostname, domain, gateways, nameservers, and proxy settings.
This record as markdown: /tools/nasbridge/network-config.md
What network_config does on Nasbridge
AI agents call network_config to retrieve information from Nasbridge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why network_config is rated Low
This tool retrieves and queries network configuration information without any side effects or state changes. It is a read-only operation that returns existing system configuration data. The low severity reflects minimal risk from exposure—understanding the network configuration could inform further attacks but does not directly enable them or cause damage. No confirmation mechanism is needed for a read operation.
From the tool's definition Tool name 'network_config' combined with description 'Get the global network configuration' indicates retrieval of configuration data.
Attacks that exploit this kind of access
The rule that runs network_config 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 network_config, this is the rule to start with:
network_config is read-only, so it stays allowed. 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 network_config call is checked against it from then on.
Questions about network_config
Get the global network configuration including hostname, domain, gateways, nameservers, and proxy settings. It is categorised as a Read tool in the Nasbridge MCP Server, which means it retrieves data without modifying state.
Register the Nasbridge MCP server in PolicyLayer and add a rule for 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 Nasbridge. Nothing to install.
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 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 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.
network_config 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