create_portal
Створити новий портал для проєкту. Портал — це клієнтський інтерфейс з меню, дашбордом і правами доступу.
This record as markdown: /tools/com-quintadb-mcp/create-portal.md
What create_portal does on QuintaDB
AI agents use create_portal 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 |
|---|---|---|---|
name | string | Yes | Назва порталу |
color | integer | — | Колір: 0=White, 1=Black, 2=Grey (дизайн/юрист), 3=Blue (корпоратив/банки), 4=Green (агро/медицина), 5=Orange (логістика/ресторани), 6=Red (авто/розваги). Суворо |
theme | integer | — | Тема: 0=Standard/Minimalist, 1=Professional, 3=Professional Opened (CRM/ERP), 4=Professional Wide, 9=Fullscreen, 11=Carbon (dark), 13=Right List, 15=Jalousie. Н |
app_id | string | Yes | Project ID (from list_projects) |
default_permissions | integer | — | 0=публічний, 1=тільки зареєстровані, 3=група |
Parameters from the server's own tool schema.
Why create_portal is rated Medium
This tool creates a new portal with configurable menus, dashboards, and access control settings. While creation is reversible (portals can be deleted), the blast radius is significant: a malicious agent could create portals that expose sensitive data to unauthorized users, bypass intended access controls, or establish persistence mechanisms within the system.
From the tool's definition Tool description states 'Створити новий портал' (create new portal), which is a creation operation. Portals manage client interfaces, menus, dashboards and access rights—structural data artifacts.
Attacks that exploit this kind of access
The rule that runs create_portal 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 create_portal, this is the rule to start with:
create_portal 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 create_portal call is checked against it from then on.
Questions about create_portal
Створити новий портал для проєкту. Портал — це клієнтський інтерфейс з меню, дашбордом і правами доступу. 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.
create_portal accepts 5 parameters: name, color, theme, app_id, default_permissions. Required: name, 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 create_portal: 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.
create_portal 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 create_portal 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 create_portal. 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.
create_portal 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