Critical Risk →

remove_dnsbl_subscription

Remove a DNSBL subscription list. Deletes the entry if no lists remain.

How to control remove_dnsbl_subscription ↓

AI agents call remove_dnsbl_subscription to permanently remove resources in OPNSense MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool irreversibly deletes DNSBL subscription configurations from the firewall, which cannot be undone without manual reconfiguration. While not data exfiltration or financial in nature, the deletion of firewall security settings is a destructive action that could degrade network security protections if misused by an agent.

From the tool's definition Tool description states 'Remove a DNSBL subscription list. Deletes the entry if no lists remain.' The use of 'Remove' and 'Deletes' indicates irreversible deletion of configuration data.

Documented attack patterns abuse exactly the kind of access remove_dnsbl_subscription 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 remove_dnsbl_subscription:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_dnsbl_subscription"
  ]
}

remove_dnsbl_subscription disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  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.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the remove_dnsbl_subscription tool do? +

Remove a DNSBL subscription list. Deletes the entry if no lists remain. It is categorised as a Destructive tool in the OPNSense MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_dnsbl_subscription? +

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

remove_dnsbl_subscription is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_dnsbl_subscription? +

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

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

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