Decrease TV volume.
AI agents invoke tv_volume_down to trigger actions in Smart Home Control 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 sends a command to a physical TV device to change its volume state. It is an Execute-category action because it triggers an external hardware operation via ADB whose effect depends on the current state of the device. It is not purely a write (no data record is created/modified in a database) and not destructive or financial.
From the tool's definition Decrease TV volume — triggers an external operation on a physical device (Android TV) via ADB
Attacks that exploit this kind of access
Decrease TV volume. It is categorised as a Execute tool in the Smart Home Control MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Smart Home Control MCP Server MCP server in PolicyLayer and add a rule for tv_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 Smart Home Control MCP Server. Nothing to install.
tv_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 tv_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 tv_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.
tv_volume_down is provided by the Smart Home Control MCP Server MCP server (surya443/smart-home-mcp-server). 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 →