Clear saved login credentials so the next connection triggers QR login.
AI agents call clear_saved_login to permanently remove resources in 米家 MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes saved authentication credentials. While credentials could be re-established via QR login, the action of clearing/deleting stored login data is a destructive operation that cannot be undone directly. Misuse by an AI agent would lock out the system from automated access, requiring manual re-authentication, making it high severity.
From the tool's definition Clear saved login credentials so the next connection triggers QR login
Documented attack patterns abuse exactly the kind of access clear_saved_login 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 clear_saved_login:
{
"version": "1",
"default": "deny",
"hide": [
"clear_saved_login"
]
} clear_saved_login disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Clear saved login credentials so the next connection triggers QR login. It is categorised as a Destructive tool in the 米家 MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 米家 MCP Server MCP server in PolicyLayer and add a rule for clear_saved_login: 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.
clear_saved_login is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_saved_login 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 clear_saved_login. 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.
clear_saved_login 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.