turn_on_light · Dual MCP Server for IoT & Memory MCP

WHAT IT DOES

What turn_on_light does on Dual MCP Server for IoT & Memory

AI agents invoke turn_on_light to trigger actions in Dual MCP Server for IoT & Memory. 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 turn_on_light needs a policy

This tool sends a command to control a physical IoT device (turning on a light bulb). It is an Execute-category action because it triggers an external real-world operation whose effect depends on the device state. While reversible (the light can be turned off), it falls under Execute rather than Write because it actuates a physical system rather than modifying data.

From the tool's definition Turn ON the light bulb — triggers an external physical operation on an IoT device

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

turn_on_light Rate-limited

turn_on_light 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": {
    "turn_on_light": {
      "limits": [
        {
          "counter": "turn_on_light_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 Dual MCP Server for IoT & Memory, so you can run agents against it safely.

FAQ

Questions about turn_on_light

What does the turn_on_light tool do? +

Turn ON the light bulb. It is categorised as a Execute tool in the Dual MCP Server for IoT & Memory MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on turn_on_light? +

Register the Dual MCP Server for IoT & Memory MCP server in PolicyLayer and add a rule for turn_on_light: 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 Dual MCP Server for IoT & Memory. Nothing to install.

What risk level is turn_on_light? +

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

Can I rate-limit turn_on_light? +

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

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

turn_on_light is provided by the Dual MCP Server for IoT & Memory MCP server (jordy33/iot_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.