Set volume. stream: music/ring/alarm/notification/system/call. volume: 0-15.
AI agents invoke set_volume to trigger actions in Android MCP Server. 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.
This tool triggers an external system operation on an Android device — adjusting the audio volume of specific streams. It is not a simple data read or write; it actively changes device hardware/system state. Misuse could include silencing ring/alarm/notification streams (e.g., suppressing alerts or calls), making it a medium-severity Execute action.
From the tool's definition Set volume. stream: music/ring/alarm/notification/system/call. volume: 0-15.
Attacks that exploit this kind of access
Set volume. stream: music/ring/alarm/notification/system/call. volume: 0-15. It is categorised as a Execute tool in the Android MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Android MCP Server 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 Android MCP Server. Nothing to install.
set_volume is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
set_volume is provided by the Android MCP Server MCP server (wujie272/android-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 →