Automated summary
Automates AbuseIPDB operations via the Rube MCP integration with Composio, dynamically discovering tools and managing connections.
Strengths
- Dynamic tool discovery via RUBE_SEARCH_TOOLS
- Automated connection management
- Pipeline execution with session reuse
- Built-in documentation for avoiding pitfalls
Limitations
- Requires Rube MCP to be configured and active
- Depends on availability of tool schemas
- Is not a standalone tool but an automation layer
To integrate AbuseIPDB into automated workflows (lookup, report IPs) with dynamic API discovery.
When you don't have access to Rube MCP or prefer to use the AbuseIPDB API directly.
Security analysis
CautionThe skill guides users to connect to an external MCP server and run tools that access Abuselpdb, which inherently involves network communication and API calls. While no destructive commands are present, the external dependencies introduce risk.
- •Instructs connection to external MCP server (rube.app) which could expose data or perform unauthorized actions if compromised
- •Enables execution of tools that interact with an external API (Abuselpdb), allowing potential data exfiltration or modification
Examples
Use Rube MCP to discover all available AbuseIPDB tools. First call RUBE_SEARCH_TOOLS with a query for AbuseIPDB operations, then check the connection status, and finally execute the 'get_blacklist' tool with a confidence threshold of 90.Automate reporting an IP address to AbuseIPDB. Use RUBE_SEARCH_TOOLS to find tools for reporting, ensure connection is ACTIVE, then execute the report tool with IP '192.0.2.1' and categories 'spam,port-scan'.name: abuselpdb-automation description: "Automate Abuselpdb tasks via Rube MCP (Composio). Always search tools first for current schemas." requires: mcp: [rube]
Abuselpdb Automation via Rube MCP
Automate Abuselpdb operations through Composio's Abuselpdb toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/abuselpdb
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Abuselpdb connection via
RUBE_MANAGE_CONNECTIONSwith toolkitabuselpdb - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitabuselpdb - 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: "Abuselpdb 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 Abuselpdb task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["abuselpdb"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Abuselpdb-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit abuselpdb |
| 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
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/abuselpdb-automation-via-rube-mcp-mmbizj65/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/abuselpdb-automation-via-rube-mcp-mmbizj65' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/abuselpdb-automation-via-rube-mcp-mmbizj65/download' --output '.skill-downloads/abuselpdb-automation-via-rube-mcp-mmbizj65/SKILL.md.part' && mv '.skill-downloads/abuselpdb-automation-via-rube-mcp-mmbizj65/SKILL.md.part' '.skill-downloads/abuselpdb-automation-via-rube-mcp-mmbizj65/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Original excerpt: Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Abuselpdb connection via
RUBE_MANAGE_CONNECTIONSwith toolkitabuselpdb - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/abuselpdb-automation-via-rube-mcp-mmbizj65/SKILL.md' && test -s '.skill-downloads/abuselpdb-automation-via-rube-mcp-mmbizj65/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/abuselpdb-automation' && cp -R '.skill-downloads/abuselpdb-automation-via-rube-mcp-mmbizj65' '.claude/skills/abuselpdb-automation'Cursor
test -f '.skill-downloads/abuselpdb-automation-via-rube-mcp-mmbizj65/SKILL.md' && test -s '.skill-downloads/abuselpdb-automation-via-rube-mcp-mmbizj65/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/abuselpdb-automation' && cp -R '.skill-downloads/abuselpdb-automation-via-rube-mcp-mmbizj65' '.cursor/skills/abuselpdb-automation'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/abuselpdb-automation-via-rube-mcp-mmbizj65'openskills read 'abuselpdb-automation-via-rube-mcp-mmbizj65'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/abuselpdb-automation-via-rube-mcp-mmbizj65/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
DeFi AMM Security
Security
Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, donation attacks, oracle manipulation, slippage, and integer math.
Semgrep Rule Creator
Security
Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Includes test-first methodology, taint mode support, and validation steps. Helps when building targeted static analysis detections.
Dev Toolbar Review Guide
Security
Safety rules for the dev toolbar, PostHog client, and feature flags. Use when reviewing changes to dev-tools and related files, covering environment guards, override cookies, and SSE stream safety.