AI agents invoke cert_letsencrypt_request 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.
Requesting a Let's Encrypt certificate triggers an external operation (ACME challenge/response with Let's Encrypt servers), modifies the firewall's certificate store, and may involve DNS or HTTP validation actions. This spans Write and Execute; Execute wins as it triggers an external automated protocol workflow with side effects beyond simple data creation.
From the tool's definition Request a Let's Encrypt certificate — triggers an external ACME protocol operation against Let's Encrypt infrastructure, involving domain validation and certificate issuance
Documented attack patterns abuse exactly the kind of access cert_letsencrypt_request 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 cert_letsencrypt_request:
{
"version": "1",
"default": "deny",
"tools": {
"cert_letsencrypt_request": {
"limits": [
{
"counter": "cert_letsencrypt_request_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}cert_letsencrypt_request 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.
Request a Let\. 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 cert_letsencrypt_request: 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.
cert_letsencrypt_request 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 cert_letsencrypt_request 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 cert_letsencrypt_request. 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.
cert_letsencrypt_request 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.