Connectors and ACC
MCP connects tools. ACC governs execution.
This page explains how Subbasis separates connector access from governed connector execution.
What this means
MCP is useful because it standardizes tool exposure and invocation patterns. But tool access alone does not guarantee safe operations. Subbasis adds ACC (Agent Connector Contract) as a governed connector contract proposal.
In practice:
- MCP helps connect tools.
- ACC governs connector use in execution.
Why it matters
An agent can call a tool, API, or internal service quickly, but speed without policy boundaries creates risk:
- wrong connector used for the operation
- unauthorized external action
- missing approval before side effects
- weak evidence for review
Governed tool use requires execution contract boundaries, not only connectivity.
How Subbasis handles it
Subbasis treats connector calls as runtime actions with policy and evidence requirements. ACC is the conceptual contract layer for this model.
Connector targets can include:
- MCP tools
- HTTP / gRPC APIs
- SaaS connectors
- internal services
Governed connector execution typically includes:
- permission scope by role and operation
- policy checks before action
- approval-aware constraints for sensitive operations
- evidence records on intent, execution, and result
- compatibility metadata for install/reuse paths
Example scenario
A support workflow wants to update CRM records.
- Agent requests CRM connector action.
- Runtime checks operation context, role permission, and active policy.
- If approval is required for data modification, workflow pauses at approval gate.
- Connector action executes only after constraints are satisfied.
- Evidence captures who requested, why, which connector path ran, and what result occurred.
An agent can use a CRM connector only if operation, permissions, policy, and approval state allow it.
What to configure
- connector/adapter registration
- role permissions per connector operation
- policy rules (allowed actions, restricted fields, escalation)
- approval gates for high-impact actions
- evidence requirements for connector calls
- compatibility tags for reusable assets
Limits and deployment notes
- ACC is described as an open connector contract proposal and architecture direction.
- Specific connector catalog and availability depend on your deployment and plan.
- Marketplace distribution and monetization are ecosystem paths; do not assume every path is fully live.