pfsense_create_services_acme_certificate_renew

WHAT IT DOES

What pfsense_create_services_acme_certificate_renew does on Pfsense

AI agents invoke pfsense_create_services_acme_certificate_renew 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_renew needs a policy

This tool initiates an ACME certificate renewal process, which is an external operation that contacts ACME servers, potentially modifies certificate files, and may restart services. It's not a simple write (creating/updating data), but rather triggers an operational workflow with side effects on running services and external systems.

From the tool's definition POST /api/v2/services/acme/certificate/renew — triggers an external certificate renewal operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pfsense_create_services_acme_certificate_renew Rate-limited

pfsense_create_services_acme_certificate_renew 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_renew": {
      "limits": [
        {
          "counter": "pfsense_create_services_acme_certificate_renew_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_renew

What does the pfsense_create_services_acme_certificate_renew tool do? +

POST /api/v2/services/acme/certificate/renew. 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_renew? +

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

pfsense_create_services_acme_certificate_renew 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_renew? +

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

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

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