Set voicing preset
AI agents use setVoicing 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 creates or modifies device configuration reversibly. Setting a voicing preset changes audio output characteristics but can be undone by selecting a different preset. It is Write (modifies device state) rather than Execute (no arbitrary code execution) or Destructive (no irreversible data loss).
From the tool's definition Tool name 'setVoicing' with description 'Set voicing preset' indicates modification of audio device settings. The server controls Lyngdorf Audio devices via TCP, and this tool modifies a configuration parameter (voicing preset) rather than reading it.
Attacks that exploit this kind of access
Set voicing preset. 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 setVoicing: 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.
setVoicing 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 setVoicing 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 setVoicing. 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.
setVoicing 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 →