Get comprehensive device status
AI agents call getStatus 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 queries and retrieves status information from Lyngdorf Audio devices with no side effects, modifications, or state changes. It is a pure read operation that returns device information, fitting the 'Read' category for retrieval operations. Severity is low as misuse would only expose audio device status information without enabling harmful actions.
From the tool's definition Tool named 'getStatus' that retrieves comprehensive device status, alongside sibling tools like getAudioStatus, getDeviceInfo, getMuteStatus, getRoomPerfect, getSource, and getStreamType which are all read operations that query device state without…
Attacks that exploit this kind of access
Get comprehensive device status. 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 getStatus: 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.
getStatus 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 getStatus 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 getStatus. 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.
getStatus 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 →