High Risk →

acme_renew_certificate

Trigger manual renewal of a specific certificate

How to control acme_renew_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.

High Risk

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:

policy.json
{
  "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.

  1. Create a free account and register OPNSense MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the acme_renew_certificate tool do? +

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.

How do I enforce a policy on acme_renew_certificate? +

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.

What risk level is acme_renew_certificate? +

acme_renew_certificate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit acme_renew_certificate? +

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.

How do I block acme_renew_certificate completely? +

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.

What MCP server provides acme_renew_certificate? +

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.

Enforce policy on every OPNSense MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.