togglePower · Lyngdorf MCP Server MCP: Risk & Policy

WHAT IT DOES

What togglePower does on Lyngdorf MCP Server

AI agents invoke togglePower to trigger actions in Lyngdorf MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why togglePower needs a policy

Toggling power is an external physical operation on a device — it triggers a real-world state change (on/off) on audio hardware via TCP. It is not purely a data read or write, and it is not destructive or financial. 'Execute' best captures triggering an external operation whose effect depends on current state. Misuse could disrupt audio playback in a live environment, hence medium severity.

From the tool's definition Toggle amplifier power state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

togglePower Rate-limited

togglePower stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "togglePower": {
      "limits": [
        {
          "counter": "togglepower_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 togglePower

What does the togglePower tool do? +

Toggle amplifier power state. It is categorised as a Execute tool in the Lyngdorf MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on togglePower? +

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

togglePower is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit togglePower? +

Yes. Add a rate_limit block to the togglePower 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 togglePower completely? +

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

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