Get current bass frequency
AI agents call getBassFrequency 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 the current bass frequency setting from a Lyngdorf audio device. It is a passive read operation that retrieves configuration state without creating, modifying, deleting, or executing any changes to the device or system. No financial, destructive, or execute-class actions are involved.
From the tool's definition Tool name 'getBassFrequency' and description 'Get current bass frequency' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get current bass frequency. 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 getBassFrequency: 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.
getBassFrequency 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 getBassFrequency 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 getBassFrequency. 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.
getBassFrequency 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 →