This record as markdown: /tools/abl030-pfsense-mcp/pfsense-get-interface-lagg.md
What pfsense_get_interface_lagg does on Pfsense
AI agents call pfsense_get_interface_lagg 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_get_interface_lagg is rated Low
This tool retrieves network interface configuration data without modifying or deleting anything. It is a read operation. However, the severity is elevated to 'medium' rather than 'low' because the retrieved information about firewall interface configurations (especially LAG settings used for high-availability and network resilience) could be sensitive network infrastructure details that an attacker could use for…
From the tool's definition Tool name 'pfsense_get_interface_lagg' and description 'GET /api/v2/interface/lagg' indicate a read-only retrieval operation using the HTTP GET method. The endpoint retrieves information about LAGG (Link Aggregation) interface configurations on pfSense.
Attacks that exploit this kind of access
The rule that runs pfsense_get_interface_lagg 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_get_interface_lagg, this is the rule to start with:
pfsense_get_interface_lagg 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_get_interface_lagg call is checked against it from then on.
Questions about pfsense_get_interface_lagg
GET /api/v2/interface/lagg. 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_get_interface_lagg: 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_get_interface_lagg 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_get_interface_lagg 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_get_interface_lagg. 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_get_interface_lagg 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