nfs_config

THE RISK

Low Risk

Why nfs_config needs a policy

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.

Documented attack patterns abuse exactly the kind of access nfs_config gives an agent:

POLICY

How to control nfs_config

PolicyLayer is an MCP gateway — it sits between your AI agents and Truenas, and nothing reaches the server without passing your rules. This is the rule we recommend for nfs_config:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "nfs_config": {}
  }
}

nfs_config is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Truenas — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Truenas tools

Destructive acme_dns_authenticator_delete Delete an ACME DNS authenticator by its ID. Destructive alertservice_delete Delete an alert notification service by its ID. Use alertservice_list to find the ID. Destructive api_key_delete Delete an API key by its numeric ID. Use api_key_list to find the ID. This immediately rev Destructive app_delete Delete/uninstall an app. This is a DESTRUCTIVE operation. The Destructive bootenv_delete Delete a boot environment. This is a DESTRUCTIVE operation — the Destructive certificate_delete Delete a certificate by its ID. This is a DESTRUCTIVE operation — the Destructive cloud_backup_delete Delete a cloud backup task (destructive — requires confirm) Destructive cloudsync_credentials_delete Delete a cloud sync credential

All 279 Truenas tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about nfs_config

What does the nfs_config tool do? +

Get global NFS configuration. It is categorised as a Read tool in the Truenas MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on nfs_config? +

Register the Truenas 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 Truenas. Nothing to install.

What risk level is nfs_config? +

nfs_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit nfs_config? +

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.

How do I block nfs_config completely? +

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.

What MCP server provides nfs_config? +

nfs_config is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Truenas tool call.

Start from Truenas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →