ws_command
Run a raw Home Assistant WebSocket command.
This record as markdown: /tools/mcp-control-plane/ws-command.md
What ws_command does on Mcp Control Plane
AI agents invoke ws_command to trigger actions in Mcp Control Plane. 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.
Why ws_command is rated High
This tool allows execution of arbitrary Home Assistant commands with effects determined entirely by user input. While not inherently destructive (depends on the command), it enables arbitrary operations on a Home Assistant system (automation, device control, state modifications). Home Assistant controls smart home devices (lights, locks, thermostats, etc.), so misuse could trigger unintended physical actions.
From the tool's definition Tool description states 'Run a raw Home Assistant WebSocket command' — this permits arbitrary command execution against a Home Assistant instance via WebSocket protocol.
Attacks that exploit this kind of access
The rule that runs ws_command safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ws_command, this is the rule to start with:
ws_command 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every ws_command call is checked against it from then on.
Questions about ws_command
Run a raw Home Assistant WebSocket command. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for ws_command: 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 Mcp Control Plane. Nothing to install.
ws_command 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 ws_command 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 ws_command. 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.
ws_command is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
Across the catalogue