AI agents invoke switch_air_purifier to trigger actions in Jenius MCP Smart Device. 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 executes a physical device operation (turning an air purifier on or off) through Home Assistant. It falls under Execute because it triggers an external operation whose effects depend on the arguments passed. It is not Destructive, Financial, or a simple data read/write. Severity is medium because misuse could affect home environment comfort or energy usage, but poses limited broader risk.
From the tool's definition 控制空气净化器的开关机流程 (Controls the air purifier's power on/off process) — triggers external device operation via Home Assistant
Documented attack patterns abuse exactly the kind of access switch_air_purifier gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jenius MCP Smart Device, and nothing reaches the server without passing your rules. This is the rule we recommend for switch_air_purifier:
{
"version": "1",
"default": "deny",
"tools": {
"switch_air_purifier": {
"limits": [
{
"counter": "switch_air_purifier_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}switch_air_purifier 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.
控制空气净化器的开关机流程。请根据用户的需求抽取参数，控制设备。. It is categorised as a Execute tool in the Jenius MCP Smart Device MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Jenius MCP Smart Device MCP server in PolicyLayer and add a rule for switch_air_purifier: 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 Jenius MCP Smart Device. Nothing to install.
switch_air_purifier 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 switch_air_purifier 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 switch_air_purifier. 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.
switch_air_purifier is provided by the Jenius MCP Smart Device MCP server (jenius-group/jenius-mcp-smart-device). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jenius MCP Smart Device, 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.
12 Jenius MCP Smart Device tools catalogued and risk-classified — across an index of 43,000+ MCP servers.