AI agents use set_mute to create or update resources in Sysprobe — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sysprobe environment.
This tool modifies audio state (mute/unmute) which is a reversible write operation. It changes system audio configuration but has no destructive, financial, or code execution implications. Misuse would at worst silence or restore audio, making it low severity.
From the tool's definition Mute or unmute the default audio sink
Attacks that exploit this kind of access
[ACTION] Mute or unmute the default audio sink. It is categorised as a Write tool in the Sysprobe MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sysprobe MCP server in PolicyLayer and add a rule for set_mute: 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.
set_mute is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_mute 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.
Set action: deny in the PolicyLayer policy for set_mute. 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.
set_mute 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →