pfsense_update_services_acme_account_key

WHAT IT DOES

What pfsense_update_services_acme_account_key does on Pfsense

AI agents use pfsense_update_services_acme_account_key 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_update_services_acme_account_key needs a policy

This tool modifies ACME account key credentials, which are sensitive authentication material used for certificate management. While reversible (Write rather than Destructive), unauthorized modification could compromise certificate renewal processes and SSL/TLS security. The high severity reflects that account keys are security-critical infrastructure components on a firewall system.

From the tool's definition Tool name indicates 'update' operation on 'services_acme_account_key' - a modification of ACME certificate account credentials.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pfsense_update_services_acme_account_key Rate-limited

pfsense_update_services_acme_account_key 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_update_services_acme_account_key": {
      "limits": [
        {
          "counter": "pfsense_update_services_acme_account_key_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_update_services_acme_account_key

What does the pfsense_update_services_acme_account_key tool do? +

pfsense_update_services_acme_account_key. 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_update_services_acme_account_key? +

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

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

Can I rate-limit pfsense_update_services_acme_account_key? +

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

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

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