Envoy MCP
Agent tools with explicit authority.
A proposed Model Context Protocol surface that lets authorized agents query catalog and coverage, prepare quotes and orders, coordinate dispatch and submit field evidence—within explicit limits.
Authentication, consent, tenant isolation and human review are part of the protocol, not an afterthought.
Tool families.
Proposed tool families and their default authority. Actual scopes are granted per tenant and role.
| Family | Example operations | Default authority |
|---|---|---|
| envoy.catalog | list_products, get_product | Read |
| envoy.coverage | check_serviceability | Authorized read |
| envoy.quotes | create_quote_draft, get_quote | Draft / read |
| envoy.sales | create_lead, update_opportunity | Bounded write |
| envoy.orders | prepare_order, submit_approved_order | Draft / approved write |
| envoy.dispatch | list_available_technicians, prepare_assignment | Read / draft |
| envoy.field | submit_completion_evidence | Scoped write |
| envoy.equipment | get_inventory, prepare_reservation | Read / draft |
| envoy.support | create_case, get_case_status | Scoped write / read |
| envoy.finance | get_commission_statement, get_invoice | Restricted read |
| envoy.training | get_certifications, list_courses | Read |
| envoy.policy | evaluate_action, get_approval_status | Policy evaluation |
Tool names and scopes are illustrative until published in the developer contract and specification.
Authority levels.
| Level | Allowed |
|---|---|
| 1 — Read and analyze | Retrieve approved information, prepare reports, identify anomalies and recommend actions. |
| 2 — Draft and prepare | Create draft quotes, schedules, messages, work orders and calculations without external commitment. |
| 3 — Bounded execution | Perform explicitly authorized actions with validation, scope limits, idempotency and required approvals. |
| 4 — High impact | Contracts, unapproved spending, pricing exceptions, regulated work, settlement, employment decisions and material customer commitments require the designated human or institutional authorization. |
The security model.
An MCP surface is an authorization boundary, not a convenience wrapper.
- Resource-specific authorization and consent
- Tenant isolation and scoped data access
- Token audience binding for HTTP flows
- Tool allowlists and least privilege
- No forwarding of provider credentials
- Execution traces and receipts
- Evaluation tests before production scopes
- Immediate revocation and suspension
Connect.
Discover capabilities
Read the tool catalog and the scopes available to the organization.
Authenticate
Establish the agent identity, accountable owner and token audience.
Select the tenant
Choose the organization and role context for the session.
Read status
Query catalog, coverage or account state before any write.
Run a sandbox query
Validate behavior with representative, non-production data.
Request approval
Escalate the consequential action to the authorized human or role.
Execute and receipt
Perform the bounded action and record the outcome.
No autonomous purchase.
A read-only query or a draft is not an order. A provider commitment requires authorization and an acknowledged response.
A predicted match is not a confirmed appointment, and a draft quote is not a price commitment.
Give the agent a boundary.
Start with read-only access, an accountable owner and a sandbox. Add authority only when the evidence supports it.
Envoy MCP is a proposed capability. Tool names, scopes and availability may change; no production MCP endpoint is promised by this page.