New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

acme_dns_authenticator_delete

Delete an ACME DNS authenticator by its ID.

SERVERNasbridge SOURCEmaverick0628/nasbridge
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nasbridge/acme-dns-authenticator-delete.md

What acme_dns_authenticator_delete does on Nasbridge

AI agents call acme_dns_authenticator_delete to permanently remove resources in Nasbridge, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why acme_dns_authenticator_delete is rated Critical

The tool permanently removes ACME DNS authenticator configuration from the system. Deleting authentication credentials/authenticators cannot be undone and would impact certificate renewal and security configurations that depend on this authenticator.

From the tool's definition Tool name contains 'delete' and description states 'Delete an ACME DNS authenticator by its ID.' This is an irreversible deletion operation.

Questions about acme_dns_authenticator_delete

What does the acme_dns_authenticator_delete tool do? +

Delete an ACME DNS authenticator by its ID. It is categorised as a Destructive tool in the Nasbridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on acme_dns_authenticator_delete? +

Register the Nasbridge MCP server in PolicyLayer and add a rule for acme_dns_authenticator_delete: 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.

What risk level is acme_dns_authenticator_delete? +

acme_dns_authenticator_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit acme_dns_authenticator_delete? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nasbridge's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.