This record as markdown: /tools/nasbridge/nfs-config.md
What nfs_config does on Nasbridge
AI agents call nfs_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 nfs_config is rated Low
The verb 'Get' explicitly indicates a read operation that queries the current NFS configuration state. This is a passive data retrieval action with no side effects, no code execution, no data modification, and no destructive capability. The low severity reflects that reading system configuration poses minimal risk; an AI agent misusing this tool would only gain visibility into NFS settings without causing harm.
From the tool's definition Tool name 'nfs_config' with description 'Get global NFS configuration' indicates retrieval of existing configuration data with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs nfs_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 nfs_config, this is the rule to start with:
nfs_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 nfs_config call is checked against it from then on.
Questions about nfs_config
Get global NFS configuration. 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 nfs_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.
nfs_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 nfs_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 nfs_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.
nfs_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