AI agents invoke control_device to trigger actions in HomeyPro 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.
The tool name 'control_device' strongly implies sending commands to physical home automation devices (lights, locks, thermostats, etc.). This constitutes executing operations on external physical systems. The description is empty, which lowers confidence, but the context of a home automation server and the 'management capabilities' mentioned in the server description support this classification.
From the tool's definition Tool name 'control_device' on a home automation server (HomeyPro) that provides 'comprehensive management capabilities'
Documented attack patterns abuse exactly the kind of access control_device gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HomeyPro MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for control_device:
{
"version": "1",
"default": "deny",
"tools": {
"control_device": {
"limits": [
{
"counter": "control_device_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}control_device 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_device. It is categorised as a Execute tool in the HomeyPro MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the HomeyPro MCP Server MCP server in PolicyLayer and add a rule for control_device: 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 HomeyPro MCP Server. Nothing to install.
control_device 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 control_device 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 control_device. 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.
control_device is provided by the HomeyPro MCP Server MCP server (pigmej/python-homey-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from HomeyPro MCP Server, 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.
19 HomeyPro MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.