How to connect Dnsfilter to OpenClaw
Connect Dnsfilter to OpenClaw with ClawLink: paste your Dnsfilter key once and 170 tools work from chat. No MCP server to run, nothing stored on your machine.
DnsfilterAPI KEYMCPDNSFilter provides cloud-based DNS security and content filtering solutions to protect networks from online threats and manage internet usage.. Once connected, OpenClaw can read and act on Dnsfilter from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Dnsfilter access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Dnsfilter setup: install one ClawHub skill, connect Dnsfilter in the browser, and OpenClaw can call real Dnsfilter actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Dnsfilter skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Dnsfilter" (hith3sh/dnsfilter-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/dnsfilter-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Dnsfilter.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Dnsfilter
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Dnsfilter?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Dnsfilter in the ClawLink dashboard — paste your Dnsfilter API key once.
Verify the connection by asking OpenClaw:
Use Dnsfilter to add allowed application and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Dnsfilter is connected in the dashboard, that agent calls the same 170 Dnsfilter tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Dnsfilter MCP for OpenClaw
Looking for a Dnsfilter MCP server for OpenClaw? ClawLink connects Dnsfilter to OpenClaw and exposes 170 Dnsfilter tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Dnsfilter integration works the same way.
What the OpenClaw Dnsfilter integration can do
170 Dnsfilter tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 170.
30 of 170 Dnsfilter tools for OpenClaw
| Tool | What it does |
|---|---|
Add allowed application dnsfilter_add_allowed_application | Adds a single application to the allow list of a policy in DNSFilter |
Add allowlist domains to policies dnsfilter_add_allowlist_domains_to_policies | Bulk add one or more domains to one or more policies' allow lists |
Add blacklist category to policy dnsfilter_add_blacklist_category_to_policy | Add a single category to a policy's blocklist |
Add blacklist domain to policy dnsfilter_add_blacklist_domain_to_policy | Add a single domain to a policy's blocklist |
Check user agent bulk updates has mixed dnsfilter_check_user_agent_bulk_updates_has_mixed | Check if user agent attributes are mixed in a bulk selection |
Create cyber sight CSV export dnsfilter_create_cyber_sight_csv_export | Creates a CyberSight CSV export record to track export of CyberSight report information |
Get API keys dnsfilter_get_api_keys | Retrieve detailed information about a specific API key by its ID |
Get application category dnsfilter_get_application_category | Retrieves detailed information about a specific DNSFilter application category by its ID |
Get billing address dnsfilter_get_billing_address | Retrieves the billing address for a specific DNSFilter organization |
Get billing information dnsfilter_get_billing_information | Retrieves billing records for a specific DNSFilter organization |
Get category dnsfilter_get_category | Get basic information of a specific category |
Get ip address dnsfilter_get_ip_address | Retrieves detailed information for a specific IP address record by its ID |
Get mac address dnsfilter_get_mac_address | Retrieves detailed information for a specific MAC address record by its ID |
Get metrics organization usage dnsfilter_get_metrics_organization_usage | Retrieves usage metrics for a DNSFilter organization over a specified date range |
Get metrics organization usage detailed dnsfilter_get_metrics_organization_usage_detailed | Retrieves detailed usage metrics for a specific DNSFilter organization |
Get my ip address dnsfilter_get_my_ip_address | Retrieve the requester's IP address as reported by DNSFilter API |
Get networks bulk create dnsfilter_get_networks_bulk_create | Check the status of a bulk network creation job |
Get networks bulk update status dnsfilter_get_networks_bulk_update_status | Check the status of a bulk network update job |
Get networks CSV export dnsfilter_get_networks_csv_export | Retrieves a networks CSV export by its ID |
Get notes dnsfilter_get_notes | Retrieve notes associated with a specific resource (policy, MSP, or organization) and domain |
Get organization dnsfilter_get_organization | Get basic information of a specific organization by ID |
Get organizations users dnsfilter_get_organizations_users | Retrieve user details and permissions for a specific organization |
Get policies dnsfilter_get_policies | Get basic information of the specified policy |
Get policies permissive mode dnsfilter_get_policies_permissive_mode | Retrieve the permissive mode setting for a specific policy |
Get policy ip dnsfilter_get_policy_ip | Retrieves basic information for a specific Policy IP by its ID |
Get scheduled report previews dnsfilter_get_scheduled_report_previews | Retrieve a specific scheduled report preview by its ID |
Get user dnsfilter_get_user | Get basic information of a specified user by ID |
Get user agent cleanup dnsfilter_get_user_agent_cleanup | Get the specific user agent cleanup by ID |
Get user agent CSV exports dnsfilter_get_user_agent_csv_exports | Retrieve a specific user agent CSV export by its ID |
Get user agents uninstall pin dnsfilter_get_user_agents_uninstall_pin | Get the uninstall PIN for an organization's user agents |
Try it: find the Dnsfilter tool you need
Browse the 30 Dnsfilter tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Dnsfilter to add allowed application and walk me through the result in plain English.
Use Dnsfilter to add allowlist domains to policies and walk me through the result in plain English.
Use Dnsfilter to add blacklist category to policy and walk me through the result in plain English.
Use Dnsfilter to add blacklist domain to policy and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Dnsfilter working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Dnsfilter API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Dnsfilter account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Dnsfilter. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Dnsfilter actions to the runtime in a format your agent can reliably use. | 170 tools for Dnsfilter are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Dnsfilter to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Dnsfilter in the browser, and the 170 tools above work from chat. There is no SDK and no config file, and the Dnsfilter key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Dnsfilter skill but can't call the tools
The ClawHub skill teaches OpenClaw about Dnsfilter, but the calls run through the ClawLink plugin and your connected account. Make sure Dnsfilter is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Dnsfilter from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Dnsfilter tools
Dnsfilter tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Dnsfilter call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Dnsfilter returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Dnsfilter has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Dnsfilter integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Dnsfilter: link your Dnsfilter account once in the browser and OpenClaw can call the Dnsfilter API through 170 ready-made tools — no custom code or token handling.
How do I add Dnsfilter to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Dnsfilter skill from ClawHub, then you click Connect in the dashboard to authorize Dnsfilter. OpenClaw calls the tools from the next message — no config files, and the Dnsfilter key you paste is stored server-side instead of in your environment.
How long does it take to connect Dnsfilter to OpenClaw?
About two minutes. Sign in, click Connect next to Dnsfilter in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Dnsfilter up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Dnsfilter working from chat.
OpenClaw installed the Dnsfilter skill but can't call the tools
The ClawHub skill teaches OpenClaw about Dnsfilter, but the calls run through the ClawLink plugin and your connected account. Make sure Dnsfilter is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
OpenClaw GitHub integration
Manage repositories, issues, pull requests, and workflows
Connect PagerDuty
Manage incidents, on-call schedules, and services
SafetyCulture tools
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.