AI agents call pfsense_list_interface_available_interfaces to retrieve information from Pfsense without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves available network interface information from the pfSense firewall via the REST API. Listing interfaces has no side effects and does not modify firewall state, routing, rules, or any configuration. While the description is empty, the naming convention clearly indicates a retrieval operation.
From the tool's definition Tool name contains 'list' and 'available_interfaces', indicating a query operation that retrieves interface information from the pfSense firewall without modification. The verb 'list' is characteristic of Read operations.
Attacks that exploit this kind of access
pfsense_list_interface_available_interfaces. 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_interface_available_interfaces: 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_interface_available_interfaces 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_interface_available_interfaces 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_interface_available_interfaces. 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_interface_available_interfaces 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →