unifi_set_dns_filtering · Multi-Tool MCP Server MCP

WHAT IT DOES

What unifi_set_dns_filtering does on Multi-Tool MCP Server

AI agents invoke unifi_set_dns_filtering to trigger actions in Multi-Tool 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 unifi_set_dns_filtering needs a policy

This tool configures DNS content filtering settings on a UniFi network controller, which is an Execute-level operation as it triggers external network configuration changes. The blast radius is high because misconfiguration could block legitimate traffic for all network users, expose users to malicious content by disabling protections, or disrupt network-wide DNS resolution.

From the tool's definition 'Configure DNS content filtering' - actively modifies network DNS filtering configuration on UniFi controller

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

unifi_set_dns_filtering Rate-limited

unifi_set_dns_filtering 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": {
    "unifi_set_dns_filtering": {
      "limits": [
        {
          "counter": "unifi_set_dns_filtering_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 Multi-Tool MCP Server, so you can run agents against it safely.

FAQ

Questions about unifi_set_dns_filtering

What does the unifi_set_dns_filtering tool do? +

Configure DNS content filtering. It is categorised as a Execute tool in the Multi-Tool 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 unifi_set_dns_filtering? +

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

What risk level is unifi_set_dns_filtering? +

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

Can I rate-limit unifi_set_dns_filtering? +

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

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

unifi_set_dns_filtering is provided by the Multi-Tool MCP Server MCP server (shawn-falconbury/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.