Sysprobe

59 tools. 19 can modify or destroy data without limits.

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

Last updated:

19 can modify or destroy data
40 read-only
59 tools total

Community server · catalogue entry verified 02/07/2026

How to control Sysprobe ↓

What Sysprobe exposes to your agents

Read (40) Write / Execute (19) Destructive / Financial (0)
High Risk

The most dangerous Sysprobe tools

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

How to control Sysprobe

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

Rate limit write operations
{
  "bluetooth_disconnect": {
    "limits": [
      {
        "counter": "bluetooth_disconnect_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "bluetooth_devices": {
    "limits": [
      {
        "counter": "bluetooth_devices_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

  1. Create a free account and register Sysprobe — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON SYSPROBE →

Instant setup, no code required.

All 59 Sysprobe tools

READ 40 tools
Read bluetooth_devices List known/paired Bluetooth devices (name + MAC). Read bluetooth_pair [ACTION] Pair (and optionally trust) a Bluetooth device. Read bluetooth_scan Scan for nearby Bluetooth devices for a few seconds. Read bluetooth_status Bluetooth adapter status (powered, discoverable, pairable). Read check_command_exists Is a CLI tool installed? Returns presence + absolute path. Read check_kernel_ring_buffer Kernel messages by level (dmesg, falls back to journalctl -k). Read diagnose_crash Inspect a coredump (coredumpctl info): signal, exe, stacktrace head. Read find_processes Find processes whose name/cmdline matches a substring. Read get_battery_health Battery health via upower: capacity, cycles, energy, state. Read get_block_devices Block devices / partitions via lsblk -J (native JSON). Read get_boot_performance Slowest units at boot (systemd-analyze blame) + total boot time. Read get_brightness Current display brightness (percent) for internal backlight(s). Read get_cpu_governor Current CPU frequency governor + the ones available. Read get_cpu_info CPU model, core counts, per-core frequency and current governor. Read get_dbus_property Read a D-Bus property (or all of an interface) via busctl. Read get_disk_usage Mounted filesystems with usage % (real disks only). Read get_gpu_info GPU summary: vendor (lspci VGA) + NVIDIA stats if nvidia-smi present. Read get_hardware_sensors Live sensors: temps, fans, battery (category 'temps'/'fans'/'battery'/'all'). Read get_kde_theme Current KDE color scheme, icon theme, look-and-feel & plasma version. Read get_now_playing Current media: player, status, artist/title (MPRIS via playerctl). Read get_power_profile Active power profile + available ones (power-profiles-daemon). Read get_process_info Detailed info for one PID: cmdline, cpu/mem, threads, open files. Read get_process_top Top resource-consuming processes (sort_by 'cpu' or 'memory'). Read get_service_status Status of a systemd unit + last few journal lines. Read get_system_info OS, kernel, uptime, CPU/mem summary, load average. One cheap call. Read get_volume Default audio sink volume & mute state (PipeWire/wpctl or pactl). Read grep_file Regex-search a single file, returning matching lines with numbers. Read inspect_process_io Open files & network connections held by a process (debug hangs). Read list_color_schemes Available KDE color schemes (for set_color_scheme). Read list_coredumps Recent application crashes (coredumpctl list). Read list_dbus_services List D-Bus names on the session or system bus (filterable). Read list_desktop_apps List installed .desktop application IDs (for launch_app). Read list_directory_tree Compact directory tree (names + sizes), depth/entry-bounded. Read list_failed_services All failed units — fastest 'what's broken?' check. Read list_pci_devices PCI devices (lspci), optionally filtered (e.g. 'VGA', 'Network'). Read list_services List systemd units. state: 'running','failed','enabled','all'. Read list_usb_devices Connected USB devices (lsusb). Read power_action [POWER] reboot / poweroff — needs SYSCONTROL_ALLOW_POWER too. Read query_journalctl query_journalctl Read read_config_snippet Read a slice of a text/config file — never the whole thing blindly.

Related servers

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

Questions about Sysprobe

How do I prevent bulk modifications through Sysprobe? +

The Sysprobe server has 3 write tools including bluetooth_disconnect, set_color_scheme, set_mute. 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 Sysprobe.

How many tools does the Sysprobe MCP server expose? +

59 tools across 3 categories: Execute, Read, Write. 40 are read-only. 19 can modify, create, or delete data.

How do I enforce a policy on Sysprobe? +

Register the Sysprobe 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 Sysprobe tool call.

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

Instant setup, no code required.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.