Control HAProxy service (start, stop, restart, reload)
AI agents invoke haproxy_service_control 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 executes service control commands on HAProxy, a critical load balancing/proxy service. While not destructive (reversible via restart), it performs Execute-class actions: triggering external operations whose effects depend on arguments (start vs. stop produce opposite outcomes). Severity is high because stopping/restarting a production load balancer could disrupt network traffic and availability.
From the tool's definition Tool name 'haproxy_service_control' with description stating it can 'start, stop, restart, reload' a service. These are operational commands that trigger external system operations whose effects are immediate and observable.
Documented attack patterns abuse exactly the kind of access haproxy_service_control 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 haproxy_service_control:
{
"version": "1",
"default": "deny",
"tools": {
"haproxy_service_control": {
"limits": [
{
"counter": "haproxy_service_control_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}haproxy_service_control 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.
Control HAProxy service (start, stop, restart, reload). 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 haproxy_service_control: 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.
haproxy_service_control 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 haproxy_service_control 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 haproxy_service_control. 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.
haproxy_service_control 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.