pfsense_replace_services_bind_sync_remote_hosts
PUT /api/v2/services/bind/sync/remote_hosts
This record as markdown: /tools/abl030-pfsense-mcp/pfsense-replace-services-bind-sync-remote-hosts.md
What pfsense_replace_services_bind_sync_remote_hosts does on Pfsense
AI agents use pfsense_replace_services_bind_sync_remote_hosts to create or update resources in Pfsense, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pfsense environment.
Why pfsense_replace_services_bind_sync_remote_hosts is rated Medium
This tool performs a reversible modification of pfSense firewall configuration (updating BIND DNS service remote hosts). While it modifies critical firewall infrastructure, it is not destructive (reversible via another PUT call) and does not delete data. The high severity reflects the broad security impact: misconfiguring DNS on a firewall could disrupt network operations or enable DNS-based attacks.
From the tool's definition Tool name contains 'replace' and description shows PUT method /api/v2/services/bind/sync/remote_hosts, which modifies DNS BIND service remote host configuration on a firewall.
Attacks that exploit this kind of access
The rule that runs pfsense_replace_services_bind_sync_remote_hosts 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_replace_services_bind_sync_remote_hosts, this is the rule to start with:
pfsense_replace_services_bind_sync_remote_hosts stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_replace_services_bind_sync_remote_hosts call is checked against it from then on.
Questions about pfsense_replace_services_bind_sync_remote_hosts
PUT /api/v2/services/bind/sync/remote_hosts. It is categorised as a Write tool in the Pfsense MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_replace_services_bind_sync_remote_hosts: 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_replace_services_bind_sync_remote_hosts is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pfsense_replace_services_bind_sync_remote_hosts 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_replace_services_bind_sync_remote_hosts. 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_replace_services_bind_sync_remote_hosts 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