Set treble frequency (1500 to 16000 Hz)
AI agents use setTrebleFrequency 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 settings (treble frequency) in a reversible manner. It is not destructive (can be changed back), not financial, not executing arbitrary code, and not reading data. It falls squarely in the Write category as it creates or modifies device configuration.
From the tool's definition Tool name 'setTrebleFrequency' indicates modification of audio settings. Description states it sets treble frequency to a specific value range (1500 to 16000 Hz), which is a parameter adjustment rather than retrieval.
Attacks that exploit this kind of access
Set treble frequency (1500 to 16000 Hz). 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 setTrebleFrequency: 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.
setTrebleFrequency 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 setTrebleFrequency 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 setTrebleFrequency. 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.
setTrebleFrequency 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 →