create_record

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 52 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-quintadb-mcp/create-record.md

WHAT IT DOES

What create_record does on QuintaDB

AI agents use create_record 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
`data`	object	—	Поля запису: { "field_id": "значення" }. КЛЮЧІ — це ID полів (наприклад "a5tfWHm8jcW47cVcSbW6Sy"), НЕ назви. Отримай їх через describe_project або get_form_fiel
`rels`	object	—	Rel-поля (зв'язки): { "field_id rel-поля": "ID запису до якого лінкувати" }. Ключ — ID rel-поля, значення — ID пов'язаного запису.
`app_id`	string	Yes	Project ID (from list_projects)
`subforms`	object	—	Subform-поля: { "field_id subform-поля": { "form_id": "ID субформи", "records": [{"field_id": "значення"}] } }. УВАГА: records має бути масивом ОБ'ЄКТІВ (hashes
`entity_id`	string	Yes	Form ID (from list_forms or describe_project)

Parameters from the server's own tool schema.

RISK

Why create_record is rated Medium

This tool creates new records in a database form, which is a reversible write operation. It does not delete, execute arbitrary code, or move money. Severity is medium because bulk record creation or injection of malicious data could affect system integrity, but individual record creation is a standard database operation with moderate blast radius.

From the tool's definition Tool name 'create_record' and description 'Створити новий запис у формі (insert row, add entry, new record)' indicate creation of data records.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_record 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_record, this is the rule to start with:

create_record Rate-limited

create_record 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_record": {
      "limits": [
        {
          "counter": "create_record_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every create_record call is checked against it from then on.

FAQ

Questions about create_record

What does the create_record tool do? +

Створити новий запис у формі (insert row, add entry, new record). ОБОВ'ЯЗКОВО: перед викликом отримай поля через describe_project або get_form_fields і використовуй field ID (не назву!) як ключі в 'data'. 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.

What parameters does create_record accept? +

create_record accepts 5 parameters: data, rels, app_id, subforms, entity_id. Required: app_id, entity_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_record? +

Register the QuintaDB MCP server in PolicyLayer and add a rule for create_record: 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.

What risk level is create_record? +

create_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_record? +

Yes. Add a rate_limit block to the create_record 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.

How do I block create_record completely? +

Set action: deny in the PolicyLayer policy for create_record. 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.

What MCP server provides create_record? +

create_record 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.

KEEP EXPLORING

More on QuintaDB, and thousands of servers like it.

This server

All 116 QuintaDB tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →