audio_sink_availability

List local PulseAudio/PipeWire sinks and whether their ports are available, respecting Omarchy speaker-tuning exclusions. Read-only.

SERVEROmarchy-MCP SOURCEhlsitechio/Omarchy-MCP

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/omarchy-mcp/audio-sink-availability.md

WHAT IT DOES

What audio_sink_availability does on Omarchy-MCP

AI agents call audio_sink_availability to retrieve information from Omarchy-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why audio_sink_availability is rated Low

Tool only lists audio sink information with no side effects or data modification capabilities.

From the tool's definition List local PulseAudio/PipeWire sinks and whether their ports are available. Read-only.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs audio_sink_availability safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Omarchy-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For audio_sink_availability, this is the rule to start with:

audio_sink_availability Allowed

audio_sink_availability is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "audio_sink_availability": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Omarchy-MCP, apply this rule, and every audio_sink_availability call is checked against it from then on.

FAQ

Questions about audio_sink_availability

What does the audio_sink_availability tool do? +

List local PulseAudio/PipeWire sinks and whether their ports are available, respecting Omarchy speaker-tuning exclusions. Read-only. It is categorised as a Read tool in the Omarchy-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on audio_sink_availability? +

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

What risk level is audio_sink_availability? +

audio_sink_availability is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit audio_sink_availability? +

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

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

audio_sink_availability is provided by the Omarchy MCP server (hlsitechio/Omarchy-MCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Omarchy, and thousands of servers like it.

This server

All 466 Omarchy tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →