Set position for any cover-capable device such as a curtain or blind.
AI agents invoke set_cover_position to trigger actions in 米家 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 triggers an external physical operation on a smart home device (curtains/blinds), changing their position in the real world. It is an Execute-category action as it actuates hardware; the effect depends on the arguments passed (position value). While reversible in principle (position can be changed again), it constitutes an external operation on physical infrastructure rather than a simple data write.
From the tool's definition Set position for any cover-capable device such as a curtain or blind
Documented attack patterns abuse exactly the kind of access set_cover_position gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 米家 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for set_cover_position:
{
"version": "1",
"default": "deny",
"tools": {
"set_cover_position": {
"limits": [
{
"counter": "set_cover_position_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}set_cover_position 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.
Set position for any cover-capable device such as a curtain or blind. It is categorised as a Execute tool in the 米家 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 米家 MCP Server MCP server in PolicyLayer and add a rule for set_cover_position: 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 Server. Nothing to install.
set_cover_position 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 set_cover_position 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 set_cover_position. 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.
set_cover_position is provided by the 米家 MCP Server MCP server (javen-yan/miot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from 米家 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.
26 米家 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.