Query device metadata (name, serial, IP, etc.)
AI agents call get_device_info to retrieve information from Moku MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static device information without modifying, deleting, executing operations, or affecting device state. It poses minimal security risk as an isolated read operation, though context (network discovery, device control) suggests the server manages hardware with potential for harm if other tools are misused. This specific tool is purely informational.
From the tool's definition Tool description explicitly states 'Query device metadata (name, serial, IP, etc.)' — a pure retrieval operation with no side effects. The verb 'Query' and the passive nature of metadata retrieval (name, serial, IP) indicate read-only access.
Attacks that exploit this kind of access
Query device metadata (name, serial, IP, etc.). It is categorised as a Read tool in the Moku MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Moku MCP Server MCP server in PolicyLayer and add a rule for get_device_info: 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 Moku MCP Server. Nothing to install.
get_device_info 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 get_device_info 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 get_device_info. 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.
get_device_info is provided by the Moku MCP Server MCP server (sealablab/moku-mcp). 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 →