AI agents invoke tuya_send_command 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.
This tool executes arbitrary custom commands on smart home devices. Because commands are fully user-defined JSON, an AI agent could trigger any device function — including potentially dangerous actions (e.g., unlocking smart locks, disabling security cameras, controlling smart appliances).
From the tool's definition Send custom commands to a Tuya device... commands must be a JSON string like: [{"code": "switch_1", "value": true}]
Attacks that exploit this kind of access
Send custom commands to a Tuya device by device_id or name (e.g. 'Living Room Light'). commands must be a JSON string like: [{"code": "switch_1", "value": true}]. 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.
Register the Tuya MCP server in PolicyLayer and add a rule for tuya_send_command: 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.
tuya_send_command 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 tuya_send_command 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 tuya_send_command. 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.
tuya_send_command 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →