This record as markdown: /tools/nasbridge/bootenv-keep.md
What bootenv_keep does on Nasbridge
AI agents use bootenv_keep 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 bootenv_keep is rated Medium
Based on the name, this tool likely sets or clears a 'keep' flag on TrueNAS boot environments, which is a reversible write operation that marks a boot environment to prevent deletion. The description is truncated so confidence is reduced. This is a Write operation as it modifies metadata/flags rather than deleting or executing code.
From the tool's definition Tool name 'bootenv_keep' suggests setting or clearing a keep flag on boot environments; description is truncated and uninformative: 'Set or clear the'
Attacks that exploit this kind of access
The rule that runs bootenv_keep 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 bootenv_keep, this is the rule to start with:
bootenv_keep 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 bootenv_keep call is checked against it from then on.
Questions about bootenv_keep
Set or clear the. 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 bootenv_keep: 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.
bootenv_keep 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 bootenv_keep 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 bootenv_keep. 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.
bootenv_keep 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