RapidClaw
Connectors, Tools, and Credentials
Connect business systems through a governed setup flow that separates discovery, credentials, permission, and approval.
Connector availability by product
| Connector | RapidClaw for OpenClaw | Product extension behavior |
|---|---|---|
| Microsoft Graph | Foundation connector configured automatically. | Shared by all RapidClaw products. |
| Business Central | Available for operator-led setup; inactive by default. | Required and automatically configured for RapidClaw for Business Central. |
| Dataverse | Available for operator-led setup; inactive by default. | Required and automatically configured for RapidClaw for RapidStart Apps. |
| Registry or custom MCP | Added through governed Connector Setup. | Available when compatible with the selected product and policy boundary. |
The governed connector setup flow
- Basics: Identify the system, purpose, owner, and intended agents.
- Authentication: Choose the supported authorization method and enter any secret only through the protected credential dialog.
- Test and discover: Verify connectivity and retrieve the tools the connector actually exposes.
- Review tools: Inspect discovered capabilities and explicitly select the tools that may be attached.
- Add or activate: Save the reviewed connector configuration and make it available only within its approved scope.
Tool names are not trusted descriptions
RapidClaw does not assume a discovered tool is safe because its name sounds read-only. Administrators review the actual discovered tool set, scope access narrowly, and apply permission and approval controls before agent use.
How credentials are protected
- Do not paste API keys, client secrets, passwords, or other raw credentials into Arcy chat.
- The protected credential dialog sends the secret directly to the authenticated server-side credential writer.
- Secret values are stored through the runtime's managed-identity path in Azure Key Vault.
- Connector configuration retains an opaque credential reference rather than the secret value.
- Raw secrets are excluded from chat, URLs, logs, browser persistence, API read responses, and dashboard rendering.
- Command Center shows non-sensitive credential metadata and status and provides controlled rotation and deletion.
Read and write boundaries
A connected system remains the system of record for its business data. RapidClaw records the operational evidence, policy decisions, approvals, audit, and memory needed to govern work; it does not silently replace Business Central or Dataverse as the authoritative business store.
- Connected-data reads can be permitted within the reviewed connector and tool scope.
- Write-capable, financial, external-communication, enablement, and destructive actions remain permission- and approval-controlled.
- Business Central starts read-first; posting operations are blocked by default.
- RapidStart Apps access is governed through the RapidClaw Dataverse connector and the selected least-privilege Dataverse application-user role.
- Removing a connector should revoke its governed runtime access without deleting unrelated data from the connected business system.
Before activating a connector
- Confirm the target tenant, environment, company, or organization is correct.
- Verify the authorization identity and least-privilege role.
- Review every enabled tool and remove capabilities the agents do not need.
- Confirm the policies and approvals for reads, writes, messages, and destructive behavior.
- Run the readiness test and begin with a narrow agent or pilot workflow.