pfsense_replace_services_acme_account_keys

PUT /api/v2/services/acme/account_keys

SERVERPfsense SOURCEabl030/pfsense-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/abl030-pfsense-mcp/pfsense-replace-services-acme-account-keys.md

WHAT IT DOES

What pfsense_replace_services_acme_account_keys does on Pfsense

AI agents use pfsense_replace_services_acme_account_keys 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.

RISK

Why pfsense_replace_services_acme_account_keys is rated Medium

PUT is a replace/overwrite operation on ACME account keys. Replacing these keys could break certificate issuance/renewal for all ACME-managed certificates on the firewall, potentially causing service outages. It is reversible in principle (keys can be restored) but has high blast radius on a firewall system.

From the tool's definition PUT /api/v2/services/acme/account_keys - replaces ACME account keys used for certificate management

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pfsense_replace_services_acme_account_keys safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pfsense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pfsense_replace_services_acme_account_keys, this is the rule to start with:

pfsense_replace_services_acme_account_keys Rate-limited

pfsense_replace_services_acme_account_keys 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_account_keys": {
      "limits": [
        {
          "counter": "pfsense_replace_services_acme_account_keys_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pfsense, apply this rule, and every pfsense_replace_services_acme_account_keys call is checked against it from then on.

FAQ

Questions about pfsense_replace_services_acme_account_keys

What does the pfsense_replace_services_acme_account_keys tool do? +

PUT /api/v2/services/acme/account_keys. 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_account_keys? +

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

pfsense_replace_services_acme_account_keys 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_account_keys? +

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

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

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

KEEP EXPLORING

More on Pfsense, and thousands of servers like it.

This server

All 680 Pfsense tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →