This record as markdown: /tools/nasbridge/nfs-config-update.md
What nfs_config_update does on Nasbridge
AI agents use nfs_config_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 nfs_config_update is rated Medium
This tool modifies NFS configuration globally, affecting network services and access controls across the TrueNAS system. While reversible (configuration can be changed back), incorrect NFS settings could disrupt network file sharing, create security vulnerabilities, or impact system availability.
From the tool's definition Tool name 'nfs_config_update' combined with description 'Update global NFS configuration' indicates modification of system configuration settings.
Attacks that exploit this kind of access
The rule that runs nfs_config_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 nfs_config_update, this is the rule to start with:
nfs_config_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 nfs_config_update call is checked against it from then on.
Questions about nfs_config_update
Update global NFS configuration. 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 nfs_config_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.
nfs_config_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 nfs_config_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 nfs_config_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.
nfs_config_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