create_record_template
Створити PDF/HTML шаблон запису. Вставляй 'html_name' поля в body БЕЗ жодних дужок (напр. Full Name). Отримай html_name через get_form_fields. Якщо шаблон з такою назвою вже є на цій формі — поверне помилку, використовуй update_record_template.
This record as markdown: /tools/com-quintadb-mcp/create-record-template.md
What create_record_template does on QuintaDB
AI agents use create_record_template 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 |
|---|---|---|---|
body | string | Yes | HTML тіло шаблону (використовуй html_name полів як звичайний текст, без дужок) |
name | string | Yes | Назва шаблону |
app_id | string | Yes | Project ID (from list_projects) |
entity_id | string | Yes | Form ID (from list_forms or describe_project) |
Parameters from the server's own tool schema.
Why create_record_template is rated Medium
The tool creates new template resources (PDF/HTML) associated with records in the database. This is a Write operation because it creates structured data that can be modified or deleted later. Severity is medium because template misconfiguration could affect document generation and user experience, but templates themselves don't directly modify core business records or cause data loss.
From the tool's definition Tool creates PDF/HTML templates for records. Description states 'Створити' (Create) and mentions that existing templates with the same name will return an error, requiring use of update_record_template instead. This is a reversible data creation operation.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs create_record_template 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_template, this is the rule to start with:
create_record_template 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_record_template call is checked against it from then on.
Questions about create_record_template
Створити PDF/HTML шаблон запису. Вставляй 'html_name' поля в body БЕЗ жодних дужок (напр. Full Name). Отримай html_name через get_form_fields. Якщо шаблон з такою назвою вже є на цій формі — поверне помилку, використовуй update_record_template. 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_record_template accepts 4 parameters: body, name, app_id, entity_id. Required: body, name, app_id, entity_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_record_template: 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_record_template 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_record_template 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_record_template. 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_record_template 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