nfs_client_count
Get the number of connected NFS clients
This record as markdown: /tools/nasbridge/nfs-client-count.md
What nfs_client_count does on Nasbridge
AI agents call nfs_client_count 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_client_count is rated Low
This tool retrieves monitoring/status information about currently connected NFS clients. It is a passive read operation that queries system state without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an AI agent calling this repeatedly would at worst cause minor performance impact from excessive monitoring queries, not data loss or system compromise.
From the tool's definition Tool name 'nfs_client_count' and description 'Get the number of connected NFS clients' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs nfs_client_count 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_client_count, this is the rule to start with:
nfs_client_count 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_client_count call is checked against it from then on.
Questions about nfs_client_count
Get the number of connected NFS clients. 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_client_count: 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_client_count 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_client_count 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_client_count. 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_client_count 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