Check the current status of the light bulb.
AI agents call check_light_status to retrieve information from Dual MCP Server for IoT & Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation—it queries and returns the current status of a light bulb without creating, modifying, deleting, or executing any actions. The verb 'check' combined with 'status' and the absence of any action-triggering language confirms this is a benign information retrieval operation with minimal security risk.
From the tool's definition Tool name 'check_light_status' and description 'Check the current status of the light bulb' indicate a query operation that retrieves state information without modification or side effects.
Attacks that exploit this kind of access
Check the current status of the light bulb. It is categorised as a Read tool in the Dual MCP Server for IoT & Memory MCP Server, which means it retrieves data without modifying state.
Register the Dual MCP Server for IoT & Memory MCP server in PolicyLayer and add a rule for check_light_status: 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.
check_light_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_light_status 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 check_light_status. 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.
check_light_status 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.
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 →