Get current audio input source
AI agents call getSource 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 reads the current audio input source configuration from a Lyngdorf Audio device. It is a pure read operation with no side effects, no code execution, and no data modification. The action is informational only, consistent with sibling tools like getAudioStatus, getBalance, getDeviceInfo, and getMuteStatus. Risk is minimal as it cannot harm the device or user data.
From the tool's definition Tool name 'getSource' and description 'Get current audio input source' indicate a query operation that retrieves the current state without modifying anything.
Attacks that exploit this kind of access
Get current audio input source. 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 getSource: 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.
getSource 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 getSource 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 getSource. 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.
getSource 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 →