upload_bios

Upload local, user-provided BIOS files into Emulation/bios via SFTP.

SERVERMcp Control Plane SOURCEalbertik322-sudo/mcp-control-plane

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-control-plane/upload-bios.md

WHAT IT DOES

What upload_bios does on Mcp Control Plane

AI agents use upload_bios to create or update resources in Mcp Control Plane, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Control Plane environment.

RISK

Why upload_bios is rated Medium

This tool creates/modifies files in a BIOS directory via SFTP, which is a Write operation. Severity is high because uploading arbitrary BIOS files could compromise system boot integrity and hardware behavior if misused by an AI agent, though the effect is technically reversible (files can be replaced or deleted).

From the tool's definition Tool description states 'Upload local, user-provided BIOS files into Emulation/bios via SFTP' — explicitly uploading files to a system directory.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs upload_bios safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upload_bios, this is the rule to start with:

upload_bios Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "upload_bios": {
      "limits": [
        {
          "counter": "upload_bios_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about upload_bios

What does the upload_bios tool do? +

Upload local, user-provided BIOS files into Emulation/bios via SFTP. It is categorised as a Write tool in the Mcp Control Plane MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on upload_bios? +

Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for upload_bios: 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 Mcp Control Plane. Nothing to install.

What risk level is upload_bios? +

upload_bios is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit upload_bios? +

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

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

upload_bios is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Control Plane, and thousands of servers like it.

This server

All 286 Mcp Control Plane tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →