adguard_toggle_protection · Homelab MCP: Risk & Policy

WHAT IT DOES

What adguard_toggle_protection does on Homelab

AI agents invoke adguard_toggle_protection to trigger actions in Homelab. 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 adguard_toggle_protection needs a policy

Toggling DNS filtering protection is an external operational action that affects network-level security. Disabling it removes DNS-based malware/ad blocking for the entire homelab network, which is a significant security impact.

From the tool's definition Enable or disable AdGuard Home DNS filtering protection

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adguard_toggle_protection Rate-limited

adguard_toggle_protection 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": {
    "adguard_toggle_protection": {
      "limits": [
        {
          "counter": "adguard_toggle_protection_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 Homelab, so you can run agents against it safely.

FAQ

Questions about adguard_toggle_protection

What does the adguard_toggle_protection tool do? +

Enable or disable AdGuard Home DNS filtering protection. It is categorised as a Execute tool in the Homelab MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on adguard_toggle_protection? +

Register the Homelab MCP server in PolicyLayer and add a rule for adguard_toggle_protection: 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 Homelab. Nothing to install.

What risk level is adguard_toggle_protection? +

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

Can I rate-limit adguard_toggle_protection? +

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

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

adguard_toggle_protection is provided by the Homelab MCP server (nainounen/homelab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.