Discover Lyngdorf devices on the network via mDNS
AI agents call discoverDevices 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.
Device discovery via mDNS is a passive, non-destructive query operation. It retrieves information about available devices on the network without side effects, state changes, or the ability to control or damage hardware. The blast radius of misuse is minimal—an attacker could only enumerate devices, not modify or delete data, execute code, or cause financial harm.
From the tool's definition The tool 'discoverDevices' uses mDNS to discover network devices. Discovery is a read-only operation that queries the network for available devices without modifying any state or triggering actions on those devices.
Attacks that exploit this kind of access
Discover Lyngdorf devices on the network via mDNS. 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 discoverDevices: 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.
discoverDevices 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 discoverDevices 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 discoverDevices. 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.
discoverDevices 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 →