set_volume · Sysprobe MCP: Risk & Policy

WHAT IT DOES

What set_volume does on Sysprobe

AI agents invoke set_volume 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_volume needs a policy

This tool triggers an external system operation (changing audio output volume) rather than simply reading or writing data. It modifies hardware/system state via an audio subsystem call. Marked as Execute because it controls a system resource; severity is medium since misuse could cause audio disruption (e.g., setting volume to 150% could damage hearing or speakers), but it is reversible.

From the tool's definition [ACTION] Set default sink volume to a percentage (0–150)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_volume Rate-limited

set_volume 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_volume": {
      "limits": [
        {
          "counter": "set_volume_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_volume

What does the set_volume tool do? +

[ACTION] Set default sink volume to a percentage (0–150). 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_volume? +

Register the Sysprobe MCP server in PolicyLayer and add a rule for set_volume: 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_volume? +

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

Can I rate-limit set_volume? +

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

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

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