Low Risk

list_available_dnsbl

List all available DNSBL subscription lists (e.g. OISD, Hagezi, Abuse.ch)

How to control list_available_dnsbl ↓

AI agents call list_available_dnsbl to retrieve information from OPNSense MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This is a straightforward query operation that retrieves informational data about available DNSBL (DNS Block List) resources. It has no side effects, does not execute commands, modify configurations, delete data, or involve financial operations. The read-only nature and absence of any mutation semantics place it firmly in the Read category with low severity.

From the tool's definition Tool name 'list_available_dnsbl' and description 'List all available DNSBL subscription lists' indicate a read-only operation that retrieves/queries data about available DNS blocklists without modifying any configuration or system state.

Documented attack patterns abuse exactly the kind of access list_available_dnsbl gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and OPNSense MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_available_dnsbl:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_available_dnsbl": {}
  }
}

list_available_dnsbl is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register OPNSense MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the list_available_dnsbl tool do? +

List all available DNSBL subscription lists (e.g. OISD, Hagezi, Abuse.ch). It is categorised as a Read tool in the OPNSense MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_available_dnsbl? +

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

What risk level is list_available_dnsbl? +

list_available_dnsbl is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_available_dnsbl? +

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

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

list_available_dnsbl is provided by the OPNSense MCP Server MCP server (vespo92/opnsensemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OPNSense MCP Server tool call.

Deterministic rules across all 196 OPNSense MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

196 OPNSense MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.