Documentation / Advanced
Govern integrations explicitly
Register the exact tool/server contract, pin its version and require only the capabilities it needs.
Inspect the local tool contract
Validate input/output schemas, execution type, timeout, idempotency and output bounds. Registered MCP servers support controlled discovery and bounded progress/results. A manifest does not install a server or grant a secret automatically.
rippflow tools validate crm.tool.yaml
rippflow tools invoke crm-update --input crm.request.json --tool-manifest crm.tool.yaml --dry-runConstrain the integration boundary
Require permission scopes and allowed principals, version/digest pins, bounded cost/concurrency and approval where needed. Use scoped secret references; do not inline credentials. Outbound destinations, redirects/private addresses and result sizes need the registered security policy.
Adapter types are not a claim that every provider is preconfigured. Use the MCP/CRM examples; download their manifest and request together.
Inspect installed registrations
These reads require an authenticated installation. Tool/MCP commands require a compatible installation (1.7.0+ in the current CLI contract).
rippflow tools list --json
rippflow mcp servers --json
rippflow operations inspect OPERATION_ID --json