boot_scrub

Start a scrub of the boot pool to check for and repair data integrity issues.

SERVERNasbridge SOURCEmaverick0628/nasbridge

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What boot_scrub does on Nasbridge

AI agents invoke boot_scrub to trigger actions in Nasbridge. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why boot_scrub is rated High

This tool triggers an active operation (scrub) on the boot pool. It executes a data integrity check and repair process, which is an external system operation. While it is intended to be beneficial (repairing data), it actively runs a system process and can modify data by repairing integrity issues.

From the tool's definition Start a scrub of the boot pool to check for and repair data integrity issues

Attacks that exploit this kind of access

RECOMMENDED RULE

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

boot_scrub Rate-limited

boot_scrub stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "boot_scrub": {
      "limits": [
        {
          "counter": "boot_scrub_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about boot_scrub

What does the boot_scrub tool do? +

Start a scrub of the boot pool to check for and repair data integrity issues. It is categorised as a Execute tool in the Nasbridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on boot_scrub? +

Register the Nasbridge MCP server in PolicyLayer and add a rule for boot_scrub: 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_scrub? +

boot_scrub is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit boot_scrub? +

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

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

boot_scrub 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →