Critical Risk →

clear_saved_login

Clear saved login credentials so the next connection triggers QR login.

How to control clear_saved_login ↓

What clear_saved_login does on 米家 MCP Server

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.

Critical Risk

Why clear_saved_login needs a policy

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:

How to control clear_saved_login

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:

policy.json
{
  "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.

  1. Create a free account and register 米家 MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about clear_saved_login

What does the clear_saved_login tool do? +

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.

How do I enforce a policy on clear_saved_login? +

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.

What risk level is clear_saved_login? +

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.

Can I rate-limit clear_saved_login? +

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.

How do I block clear_saved_login completely? +

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.

What MCP server provides clear_saved_login? +

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.

Enforce policy on every 米家 MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.