MCP server
Risk levels
Your AI client decides when to ask you before using a tool. Use these labels to set that policy. Your API key's permissions still apply either way.
| Label | What it means | Suggested policy | Tools |
|---|---|---|---|
| Costs money | Places calls or otherwise spends provider credit. | Always ask first | 11 |
| Destructive | Ends sessions, deletes data, or disconnects something you set up. | Always ask first | 5 |
| Changes data | Creates or updates data in zlicx, at no direct cost. | Ask on production accounts | 13 |
| Read only | Only reads data. | Usually safe to allow | 4 |
What isn't available over MCP
- Buying and releasing phone numbers. These need a signed-in owner or admin in the console.
- Starting or ending website widget sessions for visitors. Those belong to the visitor's browser.
- Sign-in and account authentication.
- Internal routes between zlicx services.
- Managing SIP trunks, direct MCP servers, your do-not-call list and consent records. Use the console or the REST API for these.