Tools and permissions

Kentro MCP exposes two tools of its own plus Kentro Assistant's internal tools. Which tools a connection sees, and what they return, follows the permissions of the user who approved it.

Tools

Tool	What it does	Input
`askCopilot`	Hands a question or task to Kentro Assistant, the full agent with your workspace's data, skills, memories, learnings and instincts. Best for multi-step, ambiguous or judgment-heavy requests. Returns the final answer and a `conversation_id`.	`message` (required); `conversation_id` (optional, continues a thread)
`getSessionContext`	Returns who the connection acts as, the workspace, and the tables you can query. Call it at the start of a data-heavy session.	None
The assistant's tools	Kentro Assistant's own tools, exposed directly. Fast and inexpensive for well-defined lookups.	Per tool; your client shows each schema

The assistant's tools by area. The names are examples; your client lists the current set.

Area	Example tools
Orders and fulfillment	`getOrdersSummary`, `listOrders`, `getOrderDetail`, `getFulfillmentPipeline`
Inventory and products	`getInventorySummary`, `getTopProducts`
Data queries	`listQueryableTables`, `describeTable`, `sampleTable`, `runSqlQuery`
Reports and dashboards	`listKiqReports`, `describeKiqReport`, `runKiqReport`, `listDashboards`, `createDashboard`
Knowledge base and tutorials	`searchKnowledgeBase`, `getKbArticle`, `findKbArticlesByEntity`, `listAvailableTutorials`
Conversations and learnings	`listMyConversations`, `recallConversation`, `saveCopilotLearning`
Recommendations	`getRecommendations`, `actOnFinding`

Data queries run on a read-only database connection.
Messages and scheduled tasks (sending an email or text to people in your workspace, creating a recurring report) go through askCopilot. Called directly, those tools answer that channels are not available, because they need an assistant conversation to attach to.
Two tools exist only in the Kentro web app and are not exposed: triggerInteractiveTutorial, which drives an in-app walkthrough, and renderVisualization, which draws a chart in the app.
New assistant tools appear in Kentro MCP automatically, and the server tells clients when the list changes.

How permissions apply

Every call runs as you. The connection carries the user who clicked Approve, in the workspace they approved it in. Permissions are resolved on every request, so a change to your permission groups applies to the next call.
The same access as the assistant in Kentro. The workspace must have Kentro Assistant on, and every tool checks your permissions as it does in the web app. Some tools, such as reports and finance reconciliation, check specific permissions of their own.
Help Center only. When a non-admin user's permission groups include copilot:restrict:data, the connection runs in Help Center mode: askCopilot, getSessionContext without the table list, and the knowledge base, tutorial, learning, task and messaging tools. No business data is reachable. Admins are never restricted.
One workspace. A connection reads and acts in the workspace it was approved in, and nowhere else.

askCopilot or a direct tool

Use	When
`askCopilot`	The request spans several steps or areas, needs Kentro judgment, sends a message or schedules a task, or continues an earlier assistant conversation. Kentro runs the assistant, the turn uses your workspace's assistant credit like a chat in the web app, and the conversation is saved in your assistant history.
A direct tool	A quick, well-defined lookup your AI client can reason about itself, such as one order or today's totals.

To continue a thread, pass the conversation_id from the previous askCopilot answer.

Built-in prompts

Prompt	Argument	What it asks for
`daily-ops-digest`	None	Today's new orders and revenue against yesterday, the fulfillment pipeline, inventory that needs attention and failed syncs or alerts, ending with the top three recommended actions.
`investigate-order`	`order_number`	One order end to end: status, items, fulfillment orders and warehouse routing, labels and tracking, payment state and sync with the sales channel.

Example requests

"Use getSessionContext, then list the tables I can query."
"What were yesterday's top ten products by units sold?"
"Show order 1042 with its fulfillment orders, warehouse routing and tracking numbers."
"Which inventory items need attention this week?"
"Using askCopilot, find orders unfulfilled for more than three days and explain why each one is stuck."
"Using askCopilot, create a task that emails me the fulfillment pipeline every Monday at 8:00."

Limits and messages

Situation	What the tool answers
More than 30 calls a minute or 600 a day for your user, or 120 a minute or 4,000 a day for the workspace	`Rate limit exceeded. Retry in <n>s.`
The workspace has no assistant credit left (`askCopilot`)	`This workspace is out of Copilot credit. An admin can top up in Billing.`
A tool failed	`Tool execution failed. The error has been reported.` Kentro keeps the detail in its logs.
A tool your connection may not use	`Unknown tool: <name>`