Set left/right balance (L10-L1, 0, R1-R10)
AI agents use setBalance 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 is a Write operation because it modifies device configuration reversibly (balance can be adjusted back to previous settings). It is not Read (which only queries state), not Execute (doesn't run code or trigger arbitrary operations), not Destructive (the change is reversible and doesn't erase data), and not Financial (involves no money).
From the tool's definition Tool name is 'setBalance' and description states 'Set left/right balance' — this modifies audio configuration parameters on the Lyngdorf device by adjusting the left/right stereo balance.
Attacks that exploit this kind of access
Set left/right balance (L10-L1, 0, R1-R10). 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 setBalance: 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.
setBalance 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 setBalance 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 setBalance. 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.
setBalance 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 →