setBassFrequency · Lyngdorf MCP Server MCP: Risk & Policy

WHAT IT DOES

What setBassFrequency does on Lyngdorf MCP Server

AI agents use setBassFrequency 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.

WHY IT NEEDS A POLICY

Why setBassFrequency needs a policy

This tool creates or modifies device configuration reversibly. While not destructive (the change can be undone by setting a different frequency), it does alter audio hardware state. The 'Write' category applies because it sets/updates a configurable parameter. Severity is medium because misuse could degrade audio quality or cause user annoyance, but carries no data loss, security breach, or financial risk.

From the tool's definition Tool name 'setBassFrequency' indicates it modifies audio device settings (bass frequency parameter). Description specifies parameter range (20 to 800 Hz), confirming it writes/updates a persistent device setting rather than querying state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setBassFrequency Rate-limited

setBassFrequency stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "setBassFrequency": {
      "limits": [
        {
          "counter": "setbassfrequency_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Lyngdorf MCP Server, so you can run agents against it safely.

FAQ

Questions about setBassFrequency

What does the setBassFrequency tool do? +

Set bass frequency (20 to 800 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.

How do I enforce a policy on setBassFrequency? +

Register the Lyngdorf MCP Server MCP server in PolicyLayer and add a rule for setBassFrequency: 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.

What risk level is setBassFrequency? +

setBassFrequency is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit setBassFrequency? +

Yes. Add a rate_limit block to the setBassFrequency 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.

How do I block setBassFrequency completely? +

Set action: deny in the PolicyLayer policy for setBassFrequency. 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.

What MCP server provides setBassFrequency? +

setBassFrequency 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.