AI agents call acme_revoke_certificate to permanently remove resources in OPNSense MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Certificate revocation is an irreversible action that permanently invalidates a certificate's trust status. Once revoked, the certificate cannot be reinstated and must be replaced with a new one, making this a destructive operation. The blast radius is high as revoke can cause service disruptions if the revoked certificate is actively in use for HTTPS/TLS services on the firewall or related systems.
From the tool's definition Tool name 'acme_revoke_certificate' and description 'Revoke a certificate' indicate irreversible revocation of a certificate, which cannot be undone without obtaining a new certificate.
Documented attack patterns abuse exactly the kind of access acme_revoke_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_revoke_certificate:
{
"version": "1",
"default": "deny",
"hide": [
"acme_revoke_certificate"
]
}acme_revoke_certificate disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Revoke a certificate. It is categorised as a Destructive tool in the OPNSense MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OPNSense MCP Server MCP server in PolicyLayer and add a rule for acme_revoke_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_revoke_certificate is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the acme_revoke_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_revoke_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_revoke_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.