pfsense_delete_services_acme_certificate_domain

WHAT IT DOES

What pfsense_delete_services_acme_certificate_domain does on Pfsense

AI agents call pfsense_delete_services_acme_certificate_domain to permanently remove resources in Pfsense — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

WHY IT NEEDS A POLICY

Why pfsense_delete_services_acme_certificate_domain needs a policy

This tool permanently deletes certificate domain configurations from pfSense's ACME service. Deletion is irreversible and could cause service disruption if critical certificate domains are removed. While not as critical as deleting firewall rules or user accounts, it represents an irreversible modification to security infrastructure.

From the tool's definition Tool name includes 'delete' and description shows DELETE HTTP method against /api/v2/services/acme/certificate/domain endpoint. The action irreversibly removes an ACME certificate domain configuration.

Attacks that exploit this kind of access

Questions about pfsense_delete_services_acme_certificate_domain

What does the pfsense_delete_services_acme_certificate_domain tool do? +

DELETE /api/v2/services/acme/certificate/domain. It is categorised as a Destructive tool in the Pfsense MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on pfsense_delete_services_acme_certificate_domain? +

Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_delete_services_acme_certificate_domain: 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 Pfsense. Nothing to install.

What risk level is pfsense_delete_services_acme_certificate_domain? +

pfsense_delete_services_acme_certificate_domain is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit pfsense_delete_services_acme_certificate_domain? +

Yes. Add a rate_limit block to the pfsense_delete_services_acme_certificate_domain 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 pfsense_delete_services_acme_certificate_domain completely? +

Set action: deny in the PolicyLayer policy for pfsense_delete_services_acme_certificate_domain. 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 pfsense_delete_services_acme_certificate_domain? +

pfsense_delete_services_acme_certificate_domain is provided by the Pfsense MCP server (abl030/pfsense-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.