TOOLS + CONNECTORS + MCP
Projera places tool use behind operation-level contracts and a Tool Gateway. Every call carries verified tenant and environment scope, current authority, schema, classification, policy, guardrail, budget and approval context before any external effect is dispatched.
MCP-first integration is a platform contract; connector and profile readiness stay qualification-gated.
OPERATION CONTRACTS
A tool description never grants authority. Each operation declares target system, resource type, input and output schema, required scope, data class, timeout, retry, idempotency, rollback or compensation behavior and qualification references.
TOOL GATEWAY
The gateway resolves current identity, tenant, environment, resource authorization, policy, native guardrails, quota and approval before dispatch. Direct SDK calls, sub-agents and background jobs cannot bypass the same control contract.
MCP + CONNECTORS
MCP providers and connector adapters remain replaceable behind Projera contracts. Secret values stay behind scoped references and workload identity, while the catalog exposes only the operations a product is qualified to use.
UNKNOWN OUTCOMES
Timeouts and broken connections can leave an external system in an unknown state. The runtime records outcome uncertainty, performs provider lookup or reconciliation and protects idempotency before any retry can repeat a side effect.
