What are the prerequisites to start automating Dnsfilter tasks?

You need a connected Rube MCP, an active Dnsfilter connection using the dnsfilter toolkit, and you must call RUBE_SEARCH_TOOLS first to fetch current schemas.

How do I discover available Dnsfilter tools?

Use RUBE_SEARCH_TOOLS with a use_case like 'Dnsfilter operations' to retrieve tool slugs, input schemas, and recommended execution plans before any execution.

How should I execute a tool and ensure schema compliance?

Execute the tool via RUBE_MULTI_EXECUTE_TOOL using the exact field names and types from the search results, include a memory payload (even if empty), and reuse a valid session ID.

dnsfilter-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/dnsfilter-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Dnsfilter Automation via Rube MCP

Automate Dnsfilter operations through Composio's Dnsfilter toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/dnsfilter

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Dnsfilter connection via RUBE_MANAGE_CONNECTIONS with toolkit dnsfilter
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit dnsfilter
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Dnsfilter operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Dnsfilter task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["dnsfilter"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Dnsfilter-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `dnsfilter`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/dnsfilter-automation/SKILL.mdView on GitHub

Overview

Automate Dnsfilter operations through Composio's Dnsfilter toolkit via Rube MCP. It orchestrates tool discovery, connection management, and execution of Dnsfilter actions, ensuring you always use up-to-date schemas. This approach keeps automation resilient as tool schemas evolve.

How This Skill Works

You first call RUBE_SEARCH_TOOLS to fetch current Dnsfilter tool schemas. Next, validate or establish the Dnsfilter connection with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally, execute the selected tool using RUBE_MULTI_EXECUTE_TOOL, supplying the discovered schema fields and a memory payload, while reusing session IDs when appropriate.

When to Use It

Automating recurring Dnsfilter tasks (e.g., blocklist updates, allowlist checks, or audits) using Composio's toolkit.
When tool schemas may change, requiring a fresh RUBE_SEARCH_TOOLS lookup before each run.
When establishing and validating an active Dnsfilter connection via RUBE_MANAGE_CONNECTIONS.
When you need to execute tools with exact schema fields and include a memory payload.
When performing bulk or chained operations with RUBE_MULTI_EXECUTE_TOOL and session reuse.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Run RUBE_SEARCH_TOOLS with use_case: 'Dnsfilter operations' to fetch current tool schemas.
Step 3: Run RUBE_MANAGE_CONNECTIONS for toolkit 'dnsfilter', then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and avoid hardcoding slugs.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
Use exact field names and types from the search results; don’t improvise schemas.
Include a memory parameter in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
Reuse session IDs within a workflow and paginate tool searches when responses indicate more results.

Example Use Cases

Automate daily blocklist updates by discovering the relevant Dnsfilter tool and running with a predefined memory payload.
Sync internal allowlists to Dnsfilter using the discovered tool slug and correct input schema.
Run a connectivity diagnostic workflow to verify Dnsfilter access and correct schemas.
Batch apply multiple blocklist changes in a single session using RUBE_MULTI_EXECUTE_TOOL.
Navigate tool catalogs with pagination while listing Dnsfilter actions to ensure full coverage.

Frequently Asked Questions

Add this skill to your agents