pfsense_create_services_bind_access_list_entry

A write tool on the Pfsense MCP server.

SERVERPfsense SOURCEabl030/pfsense-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/abl030-pfsense-mcp/pfsense-create-services-bind-access-list-entry.md

WHAT IT DOES

What pfsense_create_services_bind_access_list_entry does on Pfsense

AI agents use pfsense_create_services_bind_access_list_entry 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.

RISK

Why pfsense_create_services_bind_access_list_entry is rated Medium

This tool creates (writes) a new entry in pfSense's BIND DNS service access control list. While the description is empty, the 'create' action and pfSense context clearly indicate data modification. It is Write rather than Execute because it creates a configuration object rather than executing arbitrary code.

From the tool's definition Tool name contains 'create' and 'pfsense' context indicates pfSense firewall API control. Server description states it gives 'full control over pfSense firewalls' with tools covering 'services' among other firewall configurations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pfsense_create_services_bind_access_list_entry 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_create_services_bind_access_list_entry, this is the rule to start with:

pfsense_create_services_bind_access_list_entry Rate-limited

pfsense_create_services_bind_access_list_entry 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pfsense_create_services_bind_access_list_entry": {
      "limits": [
        {
          "counter": "pfsense_create_services_bind_access_list_entry_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pfsense, apply this rule, and every pfsense_create_services_bind_access_list_entry call is checked against it from then on.

FAQ

Questions about pfsense_create_services_bind_access_list_entry

What does the pfsense_create_services_bind_access_list_entry tool do? +

pfsense_create_services_bind_access_list_entry is a write tool on the Pfsense MCP server. 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.

How do I enforce a policy on pfsense_create_services_bind_access_list_entry? +

Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_create_services_bind_access_list_entry: 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.

What risk level is pfsense_create_services_bind_access_list_entry? +

pfsense_create_services_bind_access_list_entry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pfsense_create_services_bind_access_list_entry? +

Yes. Add a rate_limit block to the pfsense_create_services_bind_access_list_entry 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.

How do I block pfsense_create_services_bind_access_list_entry completely? +

Set action: deny in the PolicyLayer policy for pfsense_create_services_bind_access_list_entry. 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.

What MCP server provides pfsense_create_services_bind_access_list_entry? +

pfsense_create_services_bind_access_list_entry 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.

KEEP EXPLORING

More on Pfsense, and thousands of servers like it.

This server

All 680 Pfsense tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →