$ ~/registry/skill/composiohq-composio-skills-mx-toolbox-automation

SKILL

mx-toolbox-automation

Name: mx-toolbox-automation
Author: Composio

Automate Mx Toolbox network and email diagnostic tasks through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is essentially an open-source instruction/prompt wrapper with no bundled local code or built-in secret requirement. The main exposure comes from connecting to external Rube MCP/Composio services and acting on an authorized Mx Toolbox account, so the overall posture is low risk to caution.

CredentialsCaution

The material says no environment variables or API keys are needed, but it requires creating an ACTIVE `mx_toolbox` connection via `RUBE_MANAGE_CONNECTIONS` and possibly following an auth link. So while there is no local plaintext secret setup, it still introduces the usual third-party account authorization and session misuse risk.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to invoke Mx Toolbox tools. This means task inputs, session IDs, tool arguments, and outputs may transit through external services, but the material does not show unrelated or suspicious exfiltration endpoints.

Code executionLow risk

Per the objective checks, this is a `prompt-only` skill that provides call sequencing and argument patterns. It does not include scripts, binaries, or shell commands to install or run locally, and the material does not claim local process spawning or arbitrary code execution.

Data accessCaution

The skill itself does not request local file read/write access, but once connected to `mx_toolbox` it can perform searches, queries, or bulk actions on resources in that external service and maintain workflow context via `memory` and `session_id`. The effective data scope depends on what Mx Toolbox permissions the user grants to Composio/Rube.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (about 64.7k stars). The current material is auditable README/prompt content rather than a closed-source executable component. Although the license is undeclared and maintenance status is unknown, those are information gaps rather than red flags, and the high-trust open-source origin keeps this from being high risk.

Recommendations

Only connect after confirming trust in `rube.app/mcp` and Composio, and review their privacy and data-handling terms.
Grant only the minimum required permissions to `mx_toolbox`, preferably using a restricted test account instead of a high-privilege production account.
Verify the actual schemas returned by `RUBE_SEARCH_TOOLS` before execution to avoid mistakes caused by dynamic tool changes.
Do not place unnecessary sensitive data into session parameters, memory, or tool inputs.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Mx Toolbox Automation via Rube MCP

Automate Mx Toolbox operations through Composio's Mx Toolbox toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/mx_toolbox

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["mx_toolbox"]
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 Mx Toolbox-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `mx_toolbox`
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 Stack Exchange lookup and management tasks through Rube MCP.

ComposioGet→

$ loading_