Roborock T7 扫地机器人开始充电的触发按钮，启动后扫地机器人会归位并开始充电。
AI agents invoke start_charge_roborock_t7 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 triggers an external physical operation — commanding the Roborock T7 robot vacuum to return to its dock and start charging. It is an action that causes real-world device behavior, fitting the Execute category. The blast radius is low as it merely redirects the robot to its charging station, which is a benign and reversible action.
From the tool's definition 扫地机器人开始充电的触发按钮，启动后扫地机器人会归位并开始充电 (trigger button to start charging, robot will return to dock and begin charging)
Documented attack patterns abuse exactly the kind of access start_charge_roborock_t7 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 start_charge_roborock_t7:
{
"version": "1",
"default": "deny",
"tools": {
"start_charge_roborock_t7": {
"limits": [
{
"counter": "start_charge_roborock_t7_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}start_charge_roborock_t7 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.
Roborock T7 扫地机器人开始充电的触发按钮，启动后扫地机器人会归位并开始充电。. 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 start_charge_roborock_t7: 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.
start_charge_roborock_t7 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 start_charge_roborock_t7 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 start_charge_roborock_t7. 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.
start_charge_roborock_t7 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.