set_cpu_governor · Sysprobe MCP: Risk & Policy

WHAT IT DOES

What set_cpu_governor does on Sysprobe

AI agents invoke set_cpu_governor to trigger actions in Sysprobe. 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.

WHY IT NEEDS A POLICY

Why set_cpu_governor needs a policy

This tool modifies CPU governor settings across all cores, which is a system-level configuration change. It triggers an external operation that affects hardware behavior system-wide. While it may be reversible by resetting the governor, it can significantly impact system performance, power consumption, and stability.

From the tool's definition [ACTION] Set the CPU governor on all cores (e.g. performance, powersave)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_cpu_governor Rate-limited

set_cpu_governor 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": {
    "set_cpu_governor": {
      "limits": [
        {
          "counter": "set_cpu_governor_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sysprobe, so you can run agents against it safely.

FAQ

Questions about set_cpu_governor

What does the set_cpu_governor tool do? +

[ACTION] Set the CPU governor on all cores (e.g. performance, powersave). It is categorised as a Execute tool in the Sysprobe MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on set_cpu_governor? +

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

What risk level is set_cpu_governor? +

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

Can I rate-limit set_cpu_governor? +

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

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

set_cpu_governor is provided by the Sysprobe MCP server (raindancer118/sysprobe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

set_cpu_governor is one line of Sysprobe's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →