List all configured ACME DNS authenticators. These are used for DNS-01 challenge validation when issuing ACME certificates.
AI agents call acme_dns_authenticator_list to retrieve information from Truenas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only retrieves and displays a read-only list of ACME DNS authenticator configurations. It performs no modifications, deletions, or triggering of external actions. Even if an agent views this list, it cannot cause harmful outcomes without subsequent Write or Execute operations. The blast radius is minimal—at worst, an agent learns about existing DNS authenticator configurations.
From the tool's definition 'List all configured ACME DNS authenticators' - this is a list/query operation that retrieves existing configuration data without modification or side effects.
Documented attack patterns abuse exactly the kind of access acme_dns_authenticator_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Truenas, and nothing reaches the server without passing your rules. This is the rule we recommend for acme_dns_authenticator_list:
{
"version": "1",
"default": "deny",
"tools": {
"acme_dns_authenticator_list": {}
}
} acme_dns_authenticator_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all configured ACME DNS authenticators. These are used for DNS-01 challenge validation when issuing ACME certificates. It is categorised as a Read tool in the Truenas MCP Server, which means it retrieves data without modifying state.
Register the Truenas MCP server in PolicyLayer and add a rule for acme_dns_authenticator_list: 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 Truenas. Nothing to install.
acme_dns_authenticator_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the acme_dns_authenticator_list 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.
Set action: deny in the PolicyLayer policy for acme_dns_authenticator_list. 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.
acme_dns_authenticator_list is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Truenas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
279 Truenas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.