Permissions

The server sends your personal access token on every call. There is no service account: each operation runs as you, in your workspace, with your role, and returns what the same curl call would.

Roles

The token inherits its creator’s current role, re-read on every request, so a demotion or removal applies to the server’s next call.

Role	Can call	Refused with
`VIEWER`	Every read, plus the `validate_*` operations and `add_elevenlabs_voice`	403 `your role is view-only — ask an organization admin for editor access` on writes
`EDITOR`	Every read and write except workspace credentials	403 `only an organization admin can do this` on `create_secret`, `delete_secret`, `set_provider_key`, `delete_provider_key`
`ADMIN`	Everything the server exposes	—

The server lists every tool regardless of role; a refused call comes back as a 403. See workspaces and roles.

What the server cannot reach

These operations are not tools, so no prompt can make the server call them. Use the dashboard or the substitute.

Not exposed	Use instead
Sign-in, workspaces, members, invites, roles, personal access tokens, workspace retention setting	Dashboard. These are not in the published API the server is built from, so it cannot create or revoke a credential
Credits: balance, ledger, checkout	Dashboard. A call refused for credits reads back with `close_reason: insufficient_credits` in `get_call`
`GET /v1/conversations/{conversation_id}/events` (SSE stream)	`list_conversation_items` with `order=desc`
`stream: true` on `create_chat_message`	`create_chat_message` without it returns the whole turn
Call recording and screen-recording downloads	`get_call` reports `recording.state`; play or download in the dashboard
Deleting a call, a chat, a recording, or a call, email or WhatsApp batch	Dashboard. Each erases a record that cannot be rebuilt, and deleting a call or chat can remove a contact’s memory of it
Sending or resuming a WhatsApp batch	Dashboard, or the API directly
The chat token for a browser (`POST /v1/chats/{chat_id}/token`)	Your backend calls the API
The CoPilots’ own chat endpoints	Your client is the builder

Annotations

Every tool carries MCP annotations a client can use to decide what to auto-approve:

Annotation	Set on
`readOnlyHint`	Every `GET`
`destructiveHint`	Every `DELETE`
`idempotentHint`	`GET`, `PUT` and `DELETE`
`openWorldHint`	Never set — the server only calls the Talqing API

readOnlyHint is derived from the HTTP method. It means “changes nothing”, not “costs nothing” — and several POST operations act on the real world, below.

Approve these by hand

The server’s instructions tell the model not to publish, contact a real person, or delete unless you ask for that specific thing. That is model behaviour, not enforcement. Keep your client’s approval prompts on for these:

Operation	What happens when it runs
`create_outbound_call`	A real phone rings. Billable, cannot be recalled
`create_call_batch`, `resume_call_batch`	Up to 10,000 billable dials on a schedule. Each call runs the agent’s current published version. Voicemail is billed unless the agent has `voicemail_detection`
`add_call_batch_recipients`, `add_whatsapp_batch_recipients`	Appending to a running or completed batch contacts the new rows with no further step
`add_email_batch_recipients`, `create_email_send`	Mail can leave your Resend account to real people
`create_chat_message`	The agent runs: its tools call your endpoints and the turn is billed
`end_chat`	On Telegram or WhatsApp, the person receives whatever the agent’s exit hook says
`run_task`, `run_tool`	Executes for real against your endpoints, secrets, integrations and provider keys
`backfill_call_analysis`	One LLM call per past call in the range, on your provider key
`publish_agent`	The next call on every assigned number gets the new version
`assign_phone_number`, `unassign_phone_number`	An agent starts or stops answering real callers
Any `delete_` operation	Permanent
`set_provider_key`, `delete_provider_key`, `create_secret`, `delete_secret`	Deleting a provider key breaks every agent that needs it
`rotate_webhook_secret`	The old signing secret stops working immediately
`provision_telephony_account`, `import_phone_numbers`, `provision_phone_number`	Changes configuration in your carrier account

Tools

How tools map to API endpoints.

Recipes

Prompts that build, run and debug end to end.

MCP server

Roles

What the server cannot reach

Annotations

Approve these by hand

Next

Tools

Recipes

​Roles

​What the server cannot reach

​Annotations

​Approve these by hand

​Next

Tools

Recipes

Roles

What the server cannot reach

Annotations

Approve these by hand

Next