pfsense_services_dns_forwarder_apply
POST /api/v2/services/dns_forwarder/apply
This record as markdown: /tools/abl030-pfsense-mcp/pfsense-services-dns-forwarder-apply.md
What pfsense_services_dns_forwarder_apply does on Pfsense
AI agents invoke pfsense_services_dns_forwarder_apply to trigger actions in Pfsense. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why pfsense_services_dns_forwarder_apply is rated High
The 'apply' endpoint causes pfSense to push and activate pending DNS forwarder configuration changes, restarting or reloading the service. This is an Execute-category action: it triggers an external operational change (service restart/reload) on a network security device. Misuse could disrupt DNS resolution for all clients behind the firewall, making severity high.
From the tool's definition POST /api/v2/services/dns_forwarder/apply — 'apply' triggers an external operation that activates/restarts the DNS forwarder service on the firewall
Attacks that exploit this kind of access
The rule that runs pfsense_services_dns_forwarder_apply 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_services_dns_forwarder_apply, this is the rule to start with:
pfsense_services_dns_forwarder_apply stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_services_dns_forwarder_apply call is checked against it from then on.
Questions about pfsense_services_dns_forwarder_apply
POST /api/v2/services/dns_forwarder/apply. It is categorised as a Execute tool in the Pfsense MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_services_dns_forwarder_apply: 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_services_dns_forwarder_apply is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pfsense_services_dns_forwarder_apply 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_services_dns_forwarder_apply. 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_services_dns_forwarder_apply 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.
Across the catalogue