Control media players. Play, pause, stop, volume control, and source selection.
AI agents invoke media_player_control to trigger actions in HomeAssistant MCP. 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 real-world operations on media player devices (play, pause, stop, volume changes, source switching). These are external operations with immediate physical effects, placing it in the Execute category. Misuse could disrupt media playback or change device states, but the blast radius is limited to media devices with no data loss or financial impact.
From the tool's definition Control media players. Play, pause, stop, volume control, and source selection.
Documented attack patterns abuse exactly the kind of access media_player_control gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HomeAssistant MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for media_player_control:
{
"version": "1",
"default": "deny",
"tools": {
"media_player_control": {
"limits": [
{
"counter": "media_player_control_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}media_player_control 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.
Control media players. Play, pause, stop, volume control, and source selection. It is categorised as a Execute tool in the HomeAssistant MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the HomeAssistant MCP server in PolicyLayer and add a rule for media_player_control: 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 HomeAssistant MCP. Nothing to install.
media_player_control 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 media_player_control 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 media_player_control. 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.
media_player_control is provided by the HomeAssistant MCP server (jango-blockchained/advanced-homeassistant-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from HomeAssistant MCP, 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.
13 HomeAssistant MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.