create_form
Створити нову форму (таблицю) в існуючому проєкті. Після створення додай поля через create_field.
This record as markdown: /tools/com-quintadb-mcp/create-form.md
What create_form does on QuintaDB
AI agents use create_form 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 | Назва форми |
app_id | string | Yes | ID проєкту |
Parameters from the server's own tool schema.
Why create_form is rated Medium
The tool creates new database forms/tables within a project, which is a write operation that modifies the data structure. It is reversible (forms can be deleted) and does not irreversibly destroy data or execute arbitrary code. The medium severity reflects that an AI could create many unwanted forms, consuming resources and cluttering the database, but the impact is recoverable.
From the tool's definition Tool description states 'Створити нову форму (таблицю)' which translates to 'Create a new form (table)' — a clear data creation action. This is a reversible modification operation.
Attacks that exploit this kind of access
The rule that runs create_form 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_form, this is the rule to start with:
create_form 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_form call is checked against it from then on.
Questions about create_form
Створити нову форму (таблицю) в існуючому проєкті. Після створення додай поля через 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_form accepts 2 parameters: name, app_id. 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_form: 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_form 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_form 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_form. 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_form 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