boot_state

Get the current state of the boot pool, including disk layout, health status, and capacity.

SERVERNasbridge SOURCEmaverick0628/nasbridge

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nasbridge/boot-state.md

WHAT IT DOES

What boot_state does on Nasbridge

AI agents call boot_state 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.

RISK

Why boot_state is rated Low

This tool only retrieves information about the boot pool's state (disk layout, health, capacity). It has no side effects and performs no modifications.

From the tool's definition Get the current state of the boot pool, including disk layout, health status, and capacity.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs boot_state 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 boot_state, this is the rule to start with:

boot_state Allowed

boot_state is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every boot_state call is checked against it from then on.

FAQ

Questions about boot_state

What does the boot_state tool do? +

Get the current state of the boot pool, including disk layout, health status, and capacity. It is categorised as a Read tool in the Nasbridge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on boot_state? +

Register the Nasbridge MCP server in PolicyLayer and add a rule for boot_state: 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.

What risk level is boot_state? +

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

Can I rate-limit boot_state? +

Yes. Add a rate_limit block to the boot_state 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 boot_state completely? +

Set action: deny in the PolicyLayer policy for boot_state. 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 boot_state? +

boot_state 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.

KEEP EXPLORING

More on Nasbridge, and thousands of servers like it.

This server

All 279 Nasbridge tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →