pfsense_create_services_acme_certificate_issue

WHAT IT DOES

What pfsense_create_services_acme_certificate_issue does on Pfsense

AI agents invoke pfsense_create_services_acme_certificate_issue to trigger actions in Pfsense. 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.

WHY IT NEEDS A POLICY

Why pfsense_create_services_acme_certificate_issue needs a policy

This tool triggers an external operation (ACME certificate issuance) that involves reaching out to external certificate authorities, modifying certificate state, and potentially affecting HTTPS/TLS services on the firewall. It goes beyond a simple write as it executes an external workflow with side effects that depend on current state and external systems.

From the tool's definition POST /api/v2/services/acme/certificate/issue — 'issue' triggers an external ACME certificate issuance operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pfsense_create_services_acme_certificate_issue Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pfsense_create_services_acme_certificate_issue": {
      "limits": [
        {
          "counter": "pfsense_create_services_acme_certificate_issue_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_create_services_acme_certificate_issue

What does the pfsense_create_services_acme_certificate_issue tool do? +

POST /api/v2/services/acme/certificate/issue. It is categorised as a Execute tool in the Pfsense MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pfsense_create_services_acme_certificate_issue? +

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

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

Can I rate-limit pfsense_create_services_acme_certificate_issue? +

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

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

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