create_project
Створити новий проєкт (базу даних) з першою формою. Після створення додавай поля через create_field.
This record as markdown: /tools/com-quintadb-mcp/create-project.md
What create_project does on QuintaDB
AI agents use create_project 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 | Коротка назва проєкту (2-4 слова, не ідея, не опис). Приклад: 'Сімейний бюджет', 'CRM для клієнтів', 'Облік товарів'. |
form_name | string | — | Назва першої форми (за замовчуванням 'Main') |
Parameters from the server's own tool schema.
Why create_project is rated Medium
create_project creates new persistent database structures within the QuintaDB platform. While reversible through deletion, this is a Write operation that establishes new data containers and modifiable state. Severity is high because an AI agent could create numerous unauthorized projects, consuming resources and cluttering the system, though it does not destroy existing data or move funds.
From the tool's definition Tool description states 'Створити новий проєкт (базу даних)' which translates to 'Create a new project (database)' with an initial form. This is a creation operation that modifies the system state by adding a new database/project.
Attacks that exploit this kind of access
The rule that runs create_project 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_project, this is the rule to start with:
create_project 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_project call is checked against it from then on.
Questions about create_project
Створити новий проєкт (базу даних) з першою формою. Після створення додавай поля через create_field. 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_project accepts 2 parameters: name, form_name. Required: name. 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_project: 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_project 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_project 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_project. 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_project 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