list_devices
AI agents call list_devices 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.
List operations are inherently Read category—they retrieve or query data without causing state changes. In the IoT context, listing devices poses minimal risk; it only reveals what devices exist. Severity is low because even if misused by an agent, enumeration alone causes no damage.
From the tool's definition Tool name 'list_devices' indicates a query/retrieval operation that would enumerate IoT devices without modifying or controlling them. The pattern matches sibling tools like 'check_light_status' and 'get_all_memories' which are clearly Read category.
Attacks that exploit this kind of access
list_devices. 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 list_devices: 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.
list_devices 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 list_devices 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 list_devices. 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.
list_devices 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 →