execute_hub_tool
Execute a security tool from the hub using its identifier. Supports arguments, timeout, and file access via mounted directories; outputs are saved to a persistent volume.
Instructions
Execute a tool from a hub server.
:param identifier: Tool identifier (format: hub:server:tool or server:tool). :param arguments: Tool arguments matching the tool's input schema. :param timeout: Optional execution timeout in seconds. :return: Tool execution result.
Example identifiers:
"hub:binwalk-mcp:binwalk_scan"
"hub:yara-mcp:yara_scan_with_rules"
"hub:nmap:nmap_scan"
FILE ACCESS — if set_project_assets was called, the assets directory is mounted read-only inside the container at two standard paths:
/app/uploads/ (used by binwalk, and tools with UPLOAD_DIR)
/app/samples/ (used by yara, capa, and tools with SAMPLES_DIR) Always use /app/uploads/ or /app/samples/ when passing file paths to hub tools — do NOT use the host path.
Tool outputs are persisted to a writable shared volume:
/app/output/ (writable — extraction results, reports, etc.) Files written here survive container destruction and are available to subsequent tool calls. The host path is .secpipe/output/.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| identifier | Yes | ||
| arguments | No | ||
| timeout | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||