pfsense_get_services_dns_resolver_domain_override
GET /api/v2/services/dns_resolver/domain_override
This record as markdown: /tools/abl030-pfsense-mcp/pfsense-get-services-dns-resolver-domain-override.md
What pfsense_get_services_dns_resolver_domain_override does on Pfsense
AI agents call pfsense_get_services_dns_resolver_domain_override to retrieve information from Pfsense without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pfsense_get_services_dns_resolver_domain_override is rated Low
This tool retrieves firewall configuration data without modifying it. While the blast radius is medium (DNS overrides are security-sensitive and could inform attackers about network architecture if exposed), the operation itself is read-only. No data is created, deleted, or state is changed.
From the tool's definition Tool name contains 'get' and description shows 'GET /api/v2/' indicating a read-only API endpoint that retrieves DNS resolver domain override configuration.
Attacks that exploit this kind of access
The rule that runs pfsense_get_services_dns_resolver_domain_override safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pfsense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pfsense_get_services_dns_resolver_domain_override, this is the rule to start with:
pfsense_get_services_dns_resolver_domain_override is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Pfsense, apply this rule, and every pfsense_get_services_dns_resolver_domain_override call is checked against it from then on.
Questions about pfsense_get_services_dns_resolver_domain_override
GET /api/v2/services/dns_resolver/domain_override. It is categorised as a Read tool in the Pfsense MCP Server, which means it retrieves data without modifying state.
Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_get_services_dns_resolver_domain_override: 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 Pfsense. Nothing to install.
pfsense_get_services_dns_resolver_domain_override 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 pfsense_get_services_dns_resolver_domain_override 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 pfsense_get_services_dns_resolver_domain_override. 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.
pfsense_get_services_dns_resolver_domain_override is provided by the Pfsense MCP server (abl030/pfsense-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pfsense, and thousands of servers like it.
This server
Across the catalogue