pfsense_create_services_acme_account_key_register

WHAT IT DOES

What pfsense_create_services_acme_account_key_register does on Pfsense

AI agents invoke pfsense_create_services_acme_account_key_register 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_account_key_register needs a policy

This tool registers an ACME account key with an external Certificate Authority. While it creates data locally (Write), it also triggers an external operation (contacting the ACME CA to register), making it Execute. Misuse could result in rate-limiting by CAs, exposure of certificate infrastructure, or unauthorized certificate issuance capabilities on the firewall.

From the tool's definition POST /api/v2/services/acme/account_key/register — 'register' implies triggering an external operation (registering an ACME account key with an external CA like Let's Encrypt)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pfsense_create_services_acme_account_key_register Rate-limited

pfsense_create_services_acme_account_key_register 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_account_key_register": {
      "limits": [
        {
          "counter": "pfsense_create_services_acme_account_key_register_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_account_key_register

What does the pfsense_create_services_acme_account_key_register tool do? +

POST /api/v2/services/acme/account_key/register. 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_account_key_register? +

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

pfsense_create_services_acme_account_key_register 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_account_key_register? +

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

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

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