update_record_template

Оновити вже існуючий PDF/HTML шаблон запису (назву і/або тіло). Використовуй це, а не create_record_template, коли користувач просить 'змінити'/'оновити' вже існуючий шаблон друку — це зберігає прив'язки шаблону до кнопок друку й payment-флоу.

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 42 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What update_record_template does on QuintaDB

AI agents use update_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	—	Нове HTML тіло шаблону (опційно, html_name полів без дужок)
`name`	string	—	Нова назва шаблону (опційно)
`app_id`	string	Yes	Project ID (from list_projects)
`template_id`	string	Yes	ID шаблону запису (record template), який треба оновити

Parameters from the server's own tool schema.

RISK

Why update_record_template is rated Medium

The tool updates (modifies) existing template records, changing their name or body content. This is a Write operation—data is modified but not deleted, and changes are reversible. Severity is high because unauthorized template modifications could affect document generation, payment flows (mentioned in description), and user-facing portals across the system, potentially impacting multiple records and workflows.

From the tool's definition Tool description states 'Оновити вже існуючий PDF/HTML шаблон запису (назву і/або тіло)' — update an existing PDF/HTML template record (name and/or body). This modifies template data reversibly.

Risk signalsAccepts raw HTML/template content (body)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_record_template Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_record_template": {
      "limits": [
        {
          "counter": "update_record_template_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 update_record_template call is checked against it from then on.

FAQ

Questions about update_record_template

What does the update_record_template tool do? +

What parameters does update_record_template accept? +

update_record_template accepts 4 parameters: body, name, app_id, template_id. Required: app_id, template_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_record_template? +

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

What risk level is update_record_template? +

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

Can I rate-limit update_record_template? +

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

How do I block update_record_template completely? +

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

What MCP server provides update_record_template? +

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

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 →team_manager_record_checkpoint on Team Manager MCP → The MCP Attack Database →

Guides

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