$ ~/registry/skill/composiohq-composio-skills-abuselpdb-automation

SKILL

abuselpdb-automation

Name: abuselpdb-automation
Author: Composio

Automate AbuseIPDB lookups, reporting, and threat intel workflows via Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.9k

Summary

This is not a purely local prompt artifact: the material shows it relies on remote Rube MCP and Composio/Abuselpdb connections to discover and execute tools, so the overall posture is caution. No clear malicious red flags are evident, but the metadata conflicts with the README claims of remote connectivity and connection setup, so it should be treated as a networked third-party tool.

CredentialsCaution

The system metadata says no keys are required, but the README explicitly requires creating an active `abuselpdb` connection via `RUBE_MANAGE_CONNECTIONS` and potentially completing auth through a returned auth link; this implies third-party account authorization or tokens may be involved, even if not detailed here.

Network egressCaution

The README requires adding the remote MCP endpoint `https://rube.app/mcp` and using remote capabilities such as `RUBE_SEARCH_TOOLS`, `RUBE_MANAGE_CONNECTIONS`, and `RUBE_MULTI_EXECUTE_TOOL`; task arguments, session IDs, connection status, and potentially AbuseIPDB operation data would be sent to that service, which conflicts with the metadata claiming no remote endpoint.

Code executionCaution

The material does not show direct local arbitrary code execution, but the skill discovers and executes tools remotely through Rube MCP and references `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`; the execution boundary depends on tools and schemas returned by the remote platform rather than being fully static and visible here.

Data accessCaution

There is no explicit claim of direct local file read/write or elevated system permissions; however, it handles session data, connection state, query parameters, pagination results, and `memory` content, passing related data through a remote toolchain. The material does not show excessive local authorization, but visibility into remote data handling is limited.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (about 64.9k stars), both of which are meaningful risk-reducing signals. The current material appears to be skill documentation rather than a closed-source executable; although the license is not stated and maintenance status is unknown, there are no concrete supply-chain red flags sufficient to raise this to high risk.

Recommendations

Treat it as a networked third-party MCP skill and do not rely on the metadata claim of 'no remote endpoint/no keys' for trust decisions.
Before authorizing the `abuselpdb` connection, verify the actual OAuth/token scopes, data-sharing parties, and the privacy/logging policies of Rube and Composio.
Avoid placing unnecessary sensitive data in query arguments, memory, or workflow context.
Prefer running it in a restricted environment and log the actual endpoints contacted and data types transmitted.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "abuselpdb-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/abuselpdb-automation/SKILL.md
2. Save it as ~/.claude/skills/abuselpdb-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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_CONNECTIONS with toolkit abuselpdb
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 abuselpdb
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_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 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

Automate IP2Location lookups and geolocation workflows through Rube MCP.

ComposioGet→

$ loading_