pfsense_replace_services_acme_certificates

WHAT IT DOES

What pfsense_replace_services_acme_certificates does on Pfsense

AI agents use pfsense_replace_services_acme_certificates to create or update resources in Pfsense — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pfsense environment.

WHY IT NEEDS A POLICY

Why pfsense_replace_services_acme_certificates needs a policy

This tool modifies ACME certificate configurations on the pfSense firewall, which are essential for encrypted communications and identity verification. While not destructive (data is reversible), replacing certificates affects security posture and service availability. Categorized as Write rather than Execute because it updates a configuration resource rather than triggering arbitrary code execution.

From the tool's definition Tool name contains 'replace' and description shows PUT HTTP method to /api/v2/services/acme/certificates endpoint. PUT operations modify existing resources. ACME certificates are critical security infrastructure for TLS/SSL authentication on firewalls.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pfsense_replace_services_acme_certificates Rate-limited

pfsense_replace_services_acme_certificates stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pfsense_replace_services_acme_certificates": {
      "limits": [
        {
          "counter": "pfsense_replace_services_acme_certificates_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pfsense, so you can run agents against it safely.

FAQ

Questions about pfsense_replace_services_acme_certificates

What does the pfsense_replace_services_acme_certificates tool do? +

PUT /api/v2/services/acme/certificates. It is categorised as a Write tool in the Pfsense MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pfsense_replace_services_acme_certificates? +

Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_replace_services_acme_certificates: 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_replace_services_acme_certificates? +

pfsense_replace_services_acme_certificates is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pfsense_replace_services_acme_certificates? +

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

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

pfsense_replace_services_acme_certificates 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.