Refresh homes, devices, and room mappings from Mijia cloud.
AI agents call refresh_devices to retrieve information from 米家 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves current state information from the Mijia cloud service to update local mappings. It is a read operation that syncs data without creating, modifying, or destroying anything. The low severity reflects minimal blast radius — refreshing device lists poses no direct risk to device control or data integrity if called unexpectedly.
From the tool's definition Tool description states 'Refresh homes, devices, and room mappings from Mijia cloud' — the verb 'refresh' in this context means to retrieve or synchronize data from a remote source, not to modify or delete it. No side effects or state changes are described.
Documented attack patterns abuse exactly the kind of access refresh_devices 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 refresh_devices:
{
"version": "1",
"default": "deny",
"tools": {
"refresh_devices": {}
}
} refresh_devices is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Refresh homes, devices, and room mappings from Mijia cloud. It is categorised as a Read tool in the 米家 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 米家 MCP Server MCP server in PolicyLayer and add a rule for refresh_devices: 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.
refresh_devices is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the refresh_devices 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 refresh_devices. 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.
refresh_devices 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.