AI agents invoke volume_down to trigger actions in Vphone. 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 emulates a physical hardware button press (volume down) on a virtual iOS machine. It executes an external operation (hardware key emulation) rather than simply reading data or writing persistent data. The blast radius is low since reducing volume is a minor, easily reversible action, but it is still an Execute category action as it triggers a device-level operation.
From the tool's definition Press volume down — triggers a hardware key emulation action on the virtual iOS device
Documented attack patterns abuse exactly the kind of access volume_down gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vphone, and nothing reaches the server without passing your rules. This is the rule we recommend for volume_down:
{
"version": "1",
"default": "deny",
"tools": {
"volume_down": {
"limits": [
{
"counter": "volume_down_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}volume_down 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.
Free to start. No card required.
Press volume down. It is categorised as a Execute tool in the Vphone MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vphone MCP server in PolicyLayer and add a rule for volume_down: 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 Vphone. Nothing to install.
volume_down 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 volume_down 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 volume_down. 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.
volume_down is provided by the Vphone MCP server (pluginslab/vphone-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vphone, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Vphone tools catalogued and risk-classified — across an index of 43,000+ MCP servers.