acme_dns_authenticator_create
Create a new ACME DNS authenticator for DNS-01 challenge validation. The attributes depend on the authenticator type (e.g. Cloudflare, Route53).
This record as markdown: /tools/nasbridge/acme-dns-authenticator-create.md
What acme_dns_authenticator_create does on Nasbridge
AI agents use acme_dns_authenticator_create to create or update resources in Nasbridge, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nasbridge environment.
Why acme_dns_authenticator_create is rated Medium
This tool creates a new DNS authenticator configuration object, which is a reversible operation (it can be updated or deleted via sibling tools like acme_dns_authenticator_delete). It does not execute arbitrary code, delete data irreversibly, or handle financial transactions.
From the tool's definition Tool name contains 'create' and description states 'Create a new ACME DNS authenticator', which creates a new configuration object that can be modified or deleted later.
Attacks that exploit this kind of access
The rule that runs acme_dns_authenticator_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For acme_dns_authenticator_create, this is the rule to start with:
acme_dns_authenticator_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every acme_dns_authenticator_create call is checked against it from then on.
Questions about acme_dns_authenticator_create
Create a new ACME DNS authenticator for DNS-01 challenge validation. The attributes depend on the authenticator type (e.g. Cloudflare, Route53). It is categorised as a Write tool in the Nasbridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nasbridge MCP server in PolicyLayer and add a rule for acme_dns_authenticator_create: 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 Nasbridge. Nothing to install.
acme_dns_authenticator_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the acme_dns_authenticator_create 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_create. 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_create is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue