pfsense_list_services_dns_resolver_access_list_networks
A read tool on the Pfsense MCP server.
This record as markdown: /tools/abl030-pfsense-mcp/pfsense-list-services-dns-resolver-access-list-networks.md
What pfsense_list_services_dns_resolver_access_list_networks does on Pfsense
AI agents call pfsense_list_services_dns_resolver_access_list_networks 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_list_services_dns_resolver_access_list_networks is rated Low
The 'list' verb and structure suggest this tool retrieves DNS resolver access list network configurations from pfSense. However, the empty description reduces certainty. While retrieval of firewall/network access configurations is technically non-destructive (Read category), the blast radius is medium because DNS resolver access lists contain security-sensitive network information that could inform attacks if…
From the tool's definition Tool name contains 'list' prefix and references 'access_list_networks' which indicates querying/retrieving DNS resolver access list configurations without modification.
Attacks that exploit this kind of access
The rule that runs pfsense_list_services_dns_resolver_access_list_networks 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_list_services_dns_resolver_access_list_networks, this is the rule to start with:
pfsense_list_services_dns_resolver_access_list_networks 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_list_services_dns_resolver_access_list_networks call is checked against it from then on.
Questions about pfsense_list_services_dns_resolver_access_list_networks
pfsense_list_services_dns_resolver_access_list_networks is a read tool on the Pfsense MCP server. 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_list_services_dns_resolver_access_list_networks: 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_list_services_dns_resolver_access_list_networks 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_list_services_dns_resolver_access_list_networks 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_list_services_dns_resolver_access_list_networks. 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_list_services_dns_resolver_access_list_networks 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