configure_chat
Налаштувати кнопки зв'язку (chat widget) на порталі — WhatsApp, Telegram, email, телефон, Instagram тощо. Передай channels як об'єкт {whatsapp: '+380...', telegram: '@mybot', email: 'info@...', phone: '+380...'}.
This record as markdown: /tools/com-quintadb-mcp/configure-chat.md
What configure_chat does on QuintaDB
AI agents use configure_chat to create or update resources in QuintaDB, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QuintaDB environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
app_id | string | Yes | Project ID (from list_projects) |
channels | object | — | Канали зв'язку. Доступні ключі: whatsapp, telegram, messenger, viber, email, phone, instagram, snapchat, line, vk, sms, slack, skype, apple, linkedin, twitter, |
portal_id | string | — | ID порталу (опційно — якщо не вказано, береться перший портал) |
Parameters from the server's own tool schema.
Why configure_chat is rated Medium
This tool creates or modifies portal chat widget settings by configuring communication channels (WhatsApp, Telegram, email, phone, Instagram). This is a reversible configuration change that updates portal settings rather than executing arbitrary code or deleting data.
From the tool's definition Tool description states 'Налаштувати кнопки зв'язку (chat widget) на порталі' (configure chat widget buttons on portal) and 'Передай channels як об'єкт' (pass channels as object), indicating it modifies portal configuration by setting up communication…
Attacks that exploit this kind of access
The rule that runs configure_chat safely
PolicyLayer is an MCP gateway: it sits between your AI agents and QuintaDB, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For configure_chat, this is the rule to start with:
configure_chat stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every configure_chat call is checked against it from then on.
Questions about configure_chat
Налаштувати кнопки зв'язку (chat widget) на порталі — WhatsApp, Telegram, email, телефон, Instagram тощо. Передай channels як об'єкт {whatsapp: '+380...', telegram: '@mybot', email: 'info@...', phone: '+380...'}. It is categorised as a Write tool in the QuintaDB MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
configure_chat accepts 3 parameters: app_id, channels, portal_id. Required: app_id. The full parameter table on this page comes from the server's own tool schema.
Register the QuintaDB MCP server in PolicyLayer and add a rule for configure_chat: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches QuintaDB. Nothing to install.
configure_chat is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the configure_chat rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for configure_chat. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
configure_chat is provided by the QuintaDB MCP server (https://quintadb.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on QuintaDB, and thousands of servers like it.
This server
Across the catalogue