tuya_turn_on_device · Tuya MCP: Risk & Policy

WHAT IT DOES

What tuya_turn_on_device does on Tuya

AI agents invoke tuya_turn_on_device to trigger actions in Tuya. 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.

WHY IT NEEDS A POLICY

Why tuya_turn_on_device needs a policy

This tool sends a command to activate a physical smart home device. It has real-world side effects (powering on hardware) and its behavior depends on arguments (device_id/name, switch_code). This fits Execute as it triggers external operations. Severity is medium because misuse could turn on devices unexpectedly (lights, appliances), but it is not destructive or financial in nature.

From the tool's definition 'Turn on a Tuya device' — triggers an external physical operation on a smart home device

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tuya_turn_on_device Rate-limited

tuya_turn_on_device 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tuya_turn_on_device": {
      "limits": [
        {
          "counter": "tuya_turn_on_device_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tuya, so you can run agents against it safely.

FAQ

Questions about tuya_turn_on_device

What does the tuya_turn_on_device tool do? +

Turn on a Tuya device by device_id or name (e.g. 'Living Room Light'). For devices with multiple switches, specify switch_code (switch_1, switch_2, etc.). It is categorised as a Execute tool in the Tuya MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tuya_turn_on_device? +

Register the Tuya MCP server in PolicyLayer and add a rule for tuya_turn_on_device: 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 Tuya. Nothing to install.

What risk level is tuya_turn_on_device? +

tuya_turn_on_device is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit tuya_turn_on_device? +

Yes. Add a rate_limit block to the tuya_turn_on_device 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 tuya_turn_on_device completely? +

Set action: deny in the PolicyLayer policy for tuya_turn_on_device. 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 tuya_turn_on_device? +

tuya_turn_on_device is provided by the Tuya MCP server (juanmartinsantos/mcp-server-tuya). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.