home / skills / composiohq / awesome-claude-skills / bouncer-automation

bouncer-automation skill

safe

/bouncer-automation

This skill automates Bouncer tasks via Rube MCP, always discovering current tool schemas before execution to ensure up-to-date workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill bouncer-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: bouncer-automation
description: "Automate Bouncer tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Bouncer Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/bouncer](https://composio.dev/toolkits/bouncer)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Bouncer connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bouncer`
- 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.

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

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Bouncer 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 Bouncer task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["bouncer"]
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 Bouncer-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bouncer` |
| 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](https://composio.dev)*

Overview

This skill automates Bouncer tasks through Composio's Bouncer toolkit using Rube MCP. It provides a reliable pattern for discovering tools, validating connections, and executing Bouncer operations programmatically. The skill emphasizes always searching tools first to adapt to changing schemas and avoid hardcoded arguments.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, and execution guidance. It then ensures an active Bouncer connection via RUBE_MANAGE_CONNECTIONS and runs operations with RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH, supplying schema-compliant arguments and a memory object. Sessions are reused during workflows and refreshed for new tasks.

When to use it

Automating Bouncer workflows (blocking, allowlists, investigations) at scale
Orchestrating multi-step Bouncer operations that require tool discovery first
Running bulk or remote workbench jobs through Composio-integrated tools
Integrating Bouncer actions into larger agent workflows where schemas may change
When you need reliable session and connection management for Composio tools

Best practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and execution plans
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the bouncer toolkit before executing
Use exact schema field names and types from search results; never hardcode inputs
Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and generate new ones for separate workflows
Check for pagination tokens on search responses and continue fetching until complete

Example use cases

Find Bouncer tools to run a bulk IP block operation, then execute via RUBE_MULTI_EXECUTE_TOOL
Automate a connection setup script that verifies and completes Bouncer auth links via RUBE_MANAGE_CONNECTIONS
Run remote bulk policies with RUBE_REMOTE_WORKBENCH and run_composio_tool() for large datasets
Integrate schema discovery into an agent so it adapts when Composio updates tool inputs
Orchestrate a multi-step investigation that reuses the same session and passes memory between steps

FAQ

Do I need API keys to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client configuration; no API keys are required for basic connectivity.

What if a tool schema changes mid-workflow?

Always run RUBE_SEARCH_TOOLS before executing operations. If a schema changes, re-discover tools and adapt arguments to the returned schema before calling RUBE_MULTI_EXECUTE_TOOL.