List all RoomPerfect positions with their names from the device
AI agents call listRoomPerfectPositions to retrieve information from Lyngdorf 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 and enumerates RoomPerfect position configurations from the audio device. It has no side effects, does not execute commands, and does not modify or delete data. The 'list' verb and query-like nature align with Read category. Severity is low because exposing audio device position names poses minimal risk even if accessed by an AI agent without authorization.
From the tool's definition Tool name includes 'list' and description states 'List all RoomPerfect positions' — a query operation that retrieves configuration data without modifying device state.
Attacks that exploit this kind of access
List all RoomPerfect positions with their names from the device. It is categorised as a Read tool in the Lyngdorf MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lyngdorf MCP Server MCP server in PolicyLayer and add a rule for listRoomPerfectPositions: 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 Lyngdorf MCP Server. Nothing to install.
listRoomPerfectPositions 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 listRoomPerfectPositions 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 listRoomPerfectPositions. 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.
listRoomPerfectPositions is provided by the Lyngdorf MCP Server MCP server (thejens/lyngdorf-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 →