pool_export
Export (disconnect) a pool (destructive — requires confirm)
This record as markdown: /tools/nasbridge/pool-export.md
What pool_export does on Nasbridge
AI agents call pool_export to permanently remove resources in Nasbridge, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why pool_export is rated Critical
Exporting/disconnecting a storage pool is explicitly labeled as destructive. It disconnects the pool from the system, making all data on it inaccessible until re-imported. This operation cannot be trivially undone and could cause significant data unavailability or loss if datasets are in use, justifying a high severity rating.
From the tool's definition Export (disconnect) a pool (destructive — requires confirm)
Attacks that exploit this kind of access
The rule that runs pool_export 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 pool_export, this is the rule to start with:
pool_export is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every pool_export call is checked against it from then on.
Questions about pool_export
Export (disconnect) a pool (destructive — requires confirm). It is categorised as a Destructive tool in the Nasbridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nasbridge MCP server in PolicyLayer and add a rule for pool_export: 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.
pool_export is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pool_export 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 pool_export. 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.
pool_export 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.
Across the catalogue