This record as markdown: /tools/heznpc-airmcp/get-volume.md
What get_volume does on AirMCP
AI agents call get_volume to retrieve information from AirMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_volume is rated Low
This tool queries system audio configuration state without modifying, executing, or affecting any resources. It has minimal blast radius—an AI agent misusing it cannot cause harm beyond reading harmless system state information. Classified as Read with low severity.
From the tool's definition Tool name 'get_volume' and description 'Get the current system output volume level and mute state' indicate a retrieval operation with no side effects. The verb 'get' and the passive information retrieval (reading state) confirm this is a read-only action.
Attacks that exploit this kind of access
The rule that runs get_volume safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_volume, this is the rule to start with:
get_volume is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every get_volume call is checked against it from then on.
Questions about get_volume
Get the current system output volume level and mute state. It is categorised as a Read tool in the AirMCP MCP Server, which means it retrieves data without modifying state.
Register the Air MCP server in PolicyLayer and add a rule for get_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 AirMCP. Nothing to install.
get_volume is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_volume is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue