Nextdns for AI agents
NextDNS is a DNS-based security and privacy service that blocks malicious sites, trackers, and ads before they reach a device. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Nextdns.
Check blocked domains analytics
Pull analytics on recently blocked domains for a profile to review activity, read-only.
Add a domain to the denylist
Add a known malicious domain to a profile's denylist to block it going forward.
Approve before deleting a configuration
Require approval before deleting a NextDNS configuration, since it removes all its blocking rules.
68 Nextdns actions, graded by risk.
Every Nextdns action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
28Look things up. Allowed by default.
- nextdns.get_logsGet Logs
- nextdns.get_profileGet Profile Details
- nextdns.get_rewritesGet DNS Rewrites
- nextdns.get_settingsGet Profile Settings
- nextdns.get_allowlistGet Allowlist
- nextdns.list_profilesList Profiles
- nextdns.get_analytics_ipsGet Analytics IPs
- nextdns.get_security_tldsGet Security TLDs
- nextdns.get_settings_logsGet Logging Settings
- nextdns.get_analytics_dnssecGet Analytics DNSSEC
- nextdns.get_analytics_statusGet Analytics Status
- nextdns.get_parental_controlGet Parental Control Settings
- nextdns.get_privacy_settingsGet Privacy Settings
- nextdns.get_analytics_domainsGet Analytics Domains
- nextdns.list_denylist_domainsList Denylist Domains
- nextdns.get_analytics_devices2Get Analytics Devices
write
30Create and change things. Allow, or ask the user first.
- nextdns.add_rewriteAdd DNS Rewrite Rule
- nextdns.create_profileCreate Profile
- nextdns.add_blocked_tldAdd Blocked TLD
- nextdns.update_settingsUpdate Settings
- nextdns.update_linked_ipUpdate linked IP
- nextdns.add_privacy_nativeAdd Privacy Native Tracker
- nextdns.add_allowlist_entryAdd Allowlist Entry
- nextdns.add_denylist_domainAdd Denylist Domain
- nextdns.add_privacy_blocklistAdd Privacy Blocklist
- nextdns.update_denylist_entryUpdate Denylist Entry
- nextdns.update_allowlist_entryUpdate Allowlist Entry
- nextdns.update_parental_controlUpdate Parental Control Settings
- nextdns.update_privacy_settingsUpdate Privacy Settings
- nextdns.update_security_settingsUpdate Security Settings
- nextdns.update_settings_blockpageUpdate Block Page Settings
- nextdns.update_performance_settingsUpdate Performance Settings
destructive
10Delete, cancel or archive. Ask first, or deny outright.
- nextdns.delete_configDelete NextDNS Configuration
- nextdns.delete_rewriteDelete DNS Rewrite Rule
- nextdns.remove_blocked_tldRemove Blocked TLD
- nextdns.delete_privacy_nativeDelete Privacy Native Tracker
- nextdns.delete_allowlist_entryDelete Allowlist Entry
- nextdns.remove_denylist_domainRemove Denylist Domain
- nextdns.delete_privacy_blocklistDelete Privacy Blocklist
- nextdns.delete_parental_control_serviceDelete Parental Control Service
- nextdns.delete_parental_control_categoryDelete Parental Control Category
- nextdns.clear_logsClear Logs
Nextdns in three steps.
- 01Your users connect NextdnsThey add their Nextdns api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Profile” can wait for the user, and “delete NextDNS Configuration” can be denied outright.
- 03Any agent can actYour agent calls Nextdns through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('nextdns', { read: 'allow', write: 'ask', // create_profile destructive: 'deny', // delete_config }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Nextdns connects.
Users add their Nextdns api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Nextdns connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Nextdns from any agent.
More security and identity apps.
Nextdns and Arc0, answered.
Can I use Nextdns with Claude, ChatGPT or Cursor?
Yes. Connect Nextdns to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Nextdns actions you allow.
How do users connect Nextdns?
Users add their Nextdns api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Nextdns actions can my agent take?
68 in total: 28 read, 30 write and 10 destructive, such as “create Profile”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Nextdns?
Yes. Actions like “delete NextDNS Configuration” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Nextdns too?
Yes. The same Nextdns connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Nextdns into your agent.
Your users connect Nextdns once, under your brand. Your agent gets 68 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan