Set bass gain level (-12 to +12 dB)
AI agents use setBass to create or update resources in Lyngdorf MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lyngdorf MCP Server environment.
This tool modifies audio device state (bass equalizer setting) but the change is reversible—users can adjust the bass to any other value within the range or restore previous settings. There is no data deletion, financial transaction, or code execution involved. The scope is limited to audio tuning of a consumer audio device with no cascading effects or destructive capability.
From the tool's definition Tool name 'setBass' and description 'Set bass gain level (-12 to +12 dB)' indicate modification of audio device settings. The tool creates or modifies audio configuration data reversibly.
Attacks that exploit this kind of access
Set bass gain level (-12 to +12 dB). It is categorised as a Write tool in the Lyngdorf MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lyngdorf MCP Server MCP server in PolicyLayer and add a rule for setBass: 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.
setBass is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the setBass 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 setBass. 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.
setBass 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 →