update_template
Change an email, SMS or Telegram template that exists: its name, its text (and for email the subject, from, reply_to). Read its current text first: list_templates with kind and template_id returns it in full. A record template: update_record_template.
This record as markdown: /tools/com-quintadb-mcp/update-template.md
What update_template does on QuintaDB
AI agents use update_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 | — | The whole new text (field html_names without brackets, as in the create tool) |
from | string | — | email only |
kind | string | Yes | email | sms | telegram |
app_id | string | Yes | Project ID (from list_projects) |
subject | string | — | email only |
new_name | string | — | |
reply_to | string | — | email only |
template_id | string | Yes | From list_templates |
Parameters from the server's own tool schema.
Why update_template is rated Medium
An AI agent can call update_template faster than any human can review: one bad instruction and it creates or modifies resources in QuintaDB by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs update_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_template, this is the rule to start with:
update_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 update_template call is checked against it from then on.
Questions about update_template
Change an email, SMS or Telegram template that exists: its name, its text (and for email the subject, from, reply_to). Read its current text first: list_templates with kind and template_id returns it in full. A record template: 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.
update_template accepts 8 parameters: body, from, kind, app_id, subject, new_name, reply_to, template_id. Required: kind, app_id, template_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 update_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.
update_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 update_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 update_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.
update_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