Trigger manual renewal of a specific certificate
AI agents invoke acme_renew_certificate 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 triggers an external operation (ACME certificate renewal) whose effects depend on which certificate is targeted. While not destructive (renewal is reversible) or financial, it executes a command that interacts with external certificate authority systems.
From the tool's definition Tool name 'acme_renew_certificate' and description 'Trigger manual renewal of a specific certificate' indicate execution of a certificate renewal operation, which invokes external ACME protocol interactions and may affect firewall SSL/TLS configurations.
Documented attack patterns abuse exactly the kind of access acme_renew_certificate 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 acme_renew_certificate:
{
"version": "1",
"default": "deny",
"tools": {
"acme_renew_certificate": {
"limits": [
{
"counter": "acme_renew_certificate_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} acme_renew_certificate 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.
Trigger manual renewal of a specific certificate. 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 acme_renew_certificate: 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.
acme_renew_certificate 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 acme_renew_certificate 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 acme_renew_certificate. 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.
acme_renew_certificate 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.