Validate HAProxy configuration syntax before applying.
AI agents invoke opn_haproxy_configtest to trigger actions in OPNsense MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool runs a configuration syntax validation/test against HAProxy, which is an active execution of a diagnostic check. It doesn't read stored data passively nor write/modify anything — it triggers an external operation (config test run). The blast radius is low since it only validates and does not apply changes.
From the tool's definition Validate HAProxy configuration syntax before applying
Documented attack patterns abuse exactly the kind of access opn_haproxy_configtest 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 opn_haproxy_configtest:
{
"version": "1",
"default": "deny",
"tools": {
"opn_haproxy_configtest": {
"limits": [
{
"counter": "opn_haproxy_configtest_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} opn_haproxy_configtest stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Validate HAProxy configuration syntax before applying. It is categorised as a Execute tool in the OPNsense MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OPNsense MCP Server MCP server in PolicyLayer and add a rule for opn_haproxy_configtest: 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.
opn_haproxy_configtest is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the opn_haproxy_configtest 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 opn_haproxy_configtest. 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.
opn_haproxy_configtest is provided by the OPNsense MCP Server MCP server (lucamarien/opnsense-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OPNsense MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
81 OPNsense MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.