AI agents call search_dns_blocklist 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.
This tool performs a search operation on DNS blocklist entries, which is a read-only action that retrieves information without side effects. No data is created, modified, deleted, or financial/code execution operations are performed. The low severity reflects that misuse would only expose DNS blocklist data, not enable unauthorized changes to firewall rules or infrastructure.
From the tool's definition Tool name 'search_dns_blocklist' and description 'Search DNS blocklist entries' indicate a query/retrieval operation with no modification or execution of external commands.
Documented attack patterns abuse exactly the kind of access search_dns_blocklist 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 search_dns_blocklist:
{
"version": "1",
"default": "deny",
"tools": {
"search_dns_blocklist": {}
}
}search_dns_blocklist is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search DNS blocklist entries. It is categorised as a Read tool in the OPNSense MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OPNSense MCP Server MCP server in PolicyLayer and add a rule for search_dns_blocklist: 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.
search_dns_blocklist is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_dns_blocklist 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.
Set action: deny in the PolicyLayer policy for search_dns_blocklist. 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.
search_dns_blocklist 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.
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.