List traffic shaper pipes (bandwidth limiters)
AI agents call traffic_list_pipes to retrieve information from OPNSense MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates existing traffic shaper pipe configurations without altering system state or triggering actions. It is a straightforward informational query with no side effects, fitting the 'Read' category. Low severity because misuse would only expose firewall configuration metadata, not enable destructive actions or unauthorized network changes.
From the tool's definition Tool name contains 'list' and description states 'List traffic shaper pipes (bandwidth limiters)' - a pure query operation with no modification, deletion, or execution of arbitrary code.
Documented attack patterns abuse exactly the kind of access traffic_list_pipes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OPNSense MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for traffic_list_pipes:
{
"version": "1",
"default": "deny",
"tools": {
"traffic_list_pipes": {}
}
}traffic_list_pipes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List traffic shaper pipes (bandwidth limiters). It is categorised as a Read tool in the OPNSense MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OPNSense MCP Server MCP server in PolicyLayer and add a rule for traffic_list_pipes: 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 OPNSense MCP Server. Nothing to install.
traffic_list_pipes 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 traffic_list_pipes 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 traffic_list_pipes. 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.
traffic_list_pipes is provided by the OPNSense MCP Server MCP server (vespo92/opnsensemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 196 OPNSense MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
196 OPNSense MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.