What is the purpose of RUBE_SEARCH_TOOLS in this workflow?

To fetch current Bouncer tool schemas and slugs; avoid hardcoding and ensure up-to-date tool definitions.

What happens if the connection is not ACTIVE?

Follow the authentication flow provided by the response to activate the connection, then retry tool execution.

Do I need to include memory in multi tool execution?

Yes; memory must be included in RUBE_MULTI_EXECUTE_TOOL calls to maintain state, even if empty.

bouncer-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Bouncer Automation via Rube MCP

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

Toolkit docs: 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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit bouncer
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: "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

Source

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

Overview

Automate Bouncer operations using Composio's Bouncer toolkit through Rube MCP. It emphasizes always searching for current tool schemas before execution to keep workflows up to date. This approach ensures reliable discovery, connection management, and tool execution in repeatable, session-based processes.

How This Skill Works

Discover available Bouncer tools with RUBE_SEARCH_TOOLS to obtain current input schemas. Verify and establish the Bouncer connection via RUBE_MANAGE_CONNECTIONS, ensuring the status is ACTIVE. Execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, providing exact schema-compliant arguments, a memory payload, and a session_id.

When to Use It

When you need to automate a Bouncer operation end-to-end from discovery to execution.
When tool schemas may change and you must fetch them first with RUBE_SEARCH_TOOLS.
When performing batch executions of multiple Bouncer tools within a single session.
When establishing or validating a Bouncer connection before workflow execution.
When you need to reuse sessions and manage memory across tool executions.

Quick Start

Step 1: Verify RUBE_SEARCH_TOOLS is available and you can discover Bouncer tools using a Bouncer use_case.
Step 2: Establish or verify an ACTIVE Bouncer connection with RUBE_MANAGE_CONNECTIONS (toolkit: bouncer).
Step 3: Execute the discovered tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a valid session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before selecting tools to ensure current schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
Use exact field names and types from the discovered tool schemas.
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and handle pagination tokens if present.

Example Use Cases

Discover available Bouncer tools with RUBE_SEARCH_TOOLS for a health-check task and then execute the health tool.
Connect to Bouncer via RUBE_MANAGE_CONNECTIONS (toolkit: bouncer) and run a policy enforcement tool discovered from search results.
Batch update Bouncer configurations by executing multiple tools in one session using RUBE_MULTI_EXECUTE_TOOL with a memory payload.
Bootstrap a new Bouncer workflow by validating an ACTIVE connection and sequentially invoking required tools.
Query tool schemas with RUBE_GET_TOOL_SCHEMAS to confirm schemaRef before use.

Frequently Asked Questions

Add this skill to your agents