Governance
Safety model
MCP clients should show confirmation for actions with real-world effects. The docs generator classifies each tool from the verified API registry so reviewers can audit the exposed surface.
external-cost
Can place calls, buy numbers, or otherwise consume provider credits.
9
destructive
Can end sessions, delete state, or disconnect something already configured.
5
write
Can create or update QuickVoice data without directly costing money.
13
read
Only reads data or metadata.
6
Excluded APIs
POST /numbers
Session-only money-moving operation. Organization API keys and MCP callers cannot purchase phone numbers.
PATCH /numbers/:phId
Owner/admin session-only number management is not exposed to API-key MCP callers.
DELETE /numbers/:phId
Session-only destructive billing operation. API-key MCP callers cannot release phone numbers.
POST /calls
Internal-only server-to-server ingest; unsafe to expose to external MCP clients.
GET /agents/internal-config/:agentId
Internal runtime API requiring INTERNAL_API_KEY.
GET /agents/number-config/:phoneNumber
Internal runtime API requiring INTERNAL_API_KEY.
GET /public/widgets/:widgetId/config
Public browser widget API with origin-based CORS, not organization API-key MCP surface.
POST /public/widgets/:widgetId/sessions
Public browser call entrypoint; MCP should use admin widget APIs, not impersonate website visitors.
POST /public/widgets/:widgetId/sessions/:sessionId/end
Tied to browser session endToken, not a general MCP API.
POST /auth/*
Generated auth surface; not wrapped as domain MCP tools.
GET /docs /docs.json
Documentation/static UI, not a domain API tool/resource.
POST AI app /health, /agents/{id}/config, /voice/*, /kb/*
Internal server-to-server AI runtime APIs; they are consumed by QuickVoice API and should not be exposed directly over MCP.