// SCAN REPORT

Cimc

16 tools. 4 can modify or destroy data without limits.

4 write tools that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

4 can modify or destroy data

12 read-only

16 tools total

Community server · catalogue entry verified 03/07/2026

How to control Cimc ↓

TOOL MAP

What Cimc exposes to your agents

Read (12) Write / Execute (4) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Cimc tools

Execute · Critical power_control This tool triggers physical power state changes on a Cisco rack server — including forced power-off, hard reset, and BMC reset. Write · High set_bios_setting This tool modifies BIOS settings, which are system configuration parameters that can be changed and reverted (Write category). Write · Low set_locator_led This tool creates or modifies a physical hardware state (locator LED state) reversibly. Write · High sol_configure This tool writes/modifies the SOL configuration on the server.

4 of Cimc's 16 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Cimc

PolicyLayer is an MCP gateway — it sits between your AI agents and Cimc, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "set_bios_setting": {
    "limits": [
      {
        "counter": "set_bios_setting_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_bios_settings": {
    "limits": [
      {
        "counter": "get_bios_settings_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Cimc — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON CIMC →

Instant setup, no code required.

FULL CATALOGUE

All 16 Cimc tools

EXECUTE 1 tools

Execute power_control Control server power: on, off, graceful shutdown, power cycle, hard reset, or BMC reset. WARNING:

WRITE 3 tools

Write set_bios_setting Modify a BIOS token value. Use get_bios_settings first to discover available tokens, class names, and attribut Write set_locator_led Turn the server locator LED on or off. Used to physically identify a server in a rack. Write sol_configure Enable, disable, or configure Serial over LAN (SOL). SOL provides remote console access to the server.

READ 12 tools

Read get_bios_settings Get all current BIOS token values. Returns token names, class names, and current values needed for set_bios_se Read get_event_log Get system event log (SEL) entries from the CIMC. Shows hardware events, errors, and status changes. Read get_faults List all active faults with severity, description, cause, and timestamps. Optionally filter by severity level. Read get_firmware_versions List all component firmware versions: CIMC, BIOS, storage controllers, network adapters, etc. Read get_inventory Complete hardware inventory: CPUs, DIMMs, PCI cards, network adapters, and storage controllers. Answers Read get_network_adapters List all network adapters (NICs) with model, vendor, MAC addresses, and port details. Read get_power_stats Detailed power consumption statistics: input voltage, current, consumed power, and power budget. Read get_sensors Get all sensor readings: fans, power supplies, and temperature data from the CIMC-managed server. Read get_server_health Composite health check: server status, active faults, DIMM/PSU/fan/storage status, and power consumption. Answ Read get_server_summary Get overall server status including power state, model, serial number, CPU/memory counts, and operability. Sin Read get_storage_summary Storage subsystem overview: RAID controllers, virtual drives (arrays), and physical disks with health and stat Read get_thermal_stats Detailed thermal readings: CPU temperatures, memory temperatures, ambient, and fan speeds for all zones.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Cimc

How do I prevent bulk modifications through Cimc? +

The Cimc server has 3 write tools including set_bios_setting, set_locator_led, sol_configure. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Cimc.

How many tools does the Cimc MCP server expose? +

16 tools across 3 categories: Destructive, Read, Write. 12 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Cimc? +

Register the Cimc MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Cimc tool call.

Deterministic rules across all 16 Cimc tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CIMC →

Instant setup, no code required.

16 Cimc tools catalogued and risk-classified — across an index of 43,000+ MCP servers.