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

SKILL

brex-automation

Name: brex-automation
Author: Composio

Automate Brex account, card, and expense tasks through Rube MCP.

Stars

★ 67,807

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be an open-source prompt-style wrapper, but it is designed to drive Brex operations through the remote Rube MCP service; based on the materials, it does not directly require local API keys, so the overall posture is mainly caution. The main concern is that business data and authorization flow are delegated to the external MCP/Composio/Brex stack, while license and maintenance details are unclear.

CredentialsCaution

The material says 'No API keys needed,' but it still requires an active Brex connection via `RUBE_MANAGE_CONNECTIONS` and completion of an external auth link, which implies third-party account authorization tokens are involved, likely managed by Rube/Composio rather than locally. This creates the usual delegated-credential and misuse risks.

Network egressCaution

It explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and performing actions through Composio's Brex toolkit. Task requests, tool arguments, session information, and potentially Brex business data will be sent through that remote service chain. No unrelated or covert exfiltration endpoint is shown, but this is a standard remote data-egress scenario.

Code executionLow risk

Based on the provided material, this skill is a prompt/workflow description and does not include local script installation, shell execution, or requests for extra system privileges. Its core function is to guide use of existing MCP tools rather than directly execute code on the local machine.

Data accessCaution

Its stated purpose is to 'Automate Brex operations,' and it supports tool discovery, execution, bulk operations, and paginated retrieval, which implies access to and actions on business data in Brex accounts. There is no indication it reads local files or requests host data access beyond the automation use case, but the scope of remote business-data access may be broad and should be constrained with least privilege.

Supply chainCaution

Positive signals include a GitHub open-source source and strong community adoption (64.9k stars), which materially reduce supply-chain risk. However, this entry depends on external Rube MCP and Composio services, while the license is unspecified and maintenance status is unknown, so some caution remains warranted.

Recommendations

Only connect `https://rube.app/mcp` in a trusted environment, and confirm your organization allows Brex-related data to be processed through Rube/Composio.
Use least-privilege authorization for the Brex connection, and validate available tool scope with a test or low-privilege account first.
Manually review the schemas and arguments returned by `RUBE_SEARCH_TOOLS` before execution to avoid accidental actions on financial/payment objects.
Request clarification on licensing, maintenance status, and data-handling practices before adopting it for long-term production use.

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 "brex-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/brex-automation/SKILL.md
2. Save it as ~/.claude/skills/brex-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Brex Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/brex

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Brex connection via RUBE_MANAGE_CONNECTIONS with toolkit brex
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 brex
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: "Brex 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 Brex task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["brex"]
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 Brex-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `brex`
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 Breezy HR recruiting workflows and candidate-related tasks through Rube MCP.

ComposioGet→

$ loading_