List all available input sources with their actual names from the device
AI agents call listSources 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 returns data about the audio device's available sources without modifying any device state, settings, or configuration. It has no side effects and poses minimal security risk—merely exposing what input options are available on the device. This is purely informational retrieval, consistent with sibling tools like 'getAudioStatus' and 'getDeviceInfo' that are clearly Read-category operations.
From the tool's definition The tool 'listSources' retrieves information about available input sources with their actual names from the device. The verb 'list' indicates a retrieval operation with no state modification capability.
Attacks that exploit this kind of access
List all available input sources with their actual 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 listSources: 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.
listSources 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 listSources 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 listSources. 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.
listSources 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 →