list_templates
Список шаблонів: record, email, sms. Якщо kind не вказано — повертає всі типи.
This record as markdown: /tools/com-quintadb-mcp/list-templates.md
What list_templates does on QuintaDB
AI agents call list_templates to retrieve information from QuintaDB without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
kind | string | — | record | email | sms (default: всі) |
app_id | string | Yes | Project ID (from list_projects) |
entity_id | string | — | Опційно — фільтр по формі |
Parameters from the server's own tool schema.
Why list_templates is rated Low
This tool performs a query/list operation that retrieves template metadata. It has no side effects—it does not create, modify, delete, or execute anything. It simply returns information about available templates in the system. This is a classic Read operation with minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'list_templates' and description 'List templates: record, email, sms. If kind is not specified — returns all types.' indicates retrieval/enumeration of existing templates with no modification or execution.
Attacks that exploit this kind of access
The rule that runs list_templates 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 list_templates, this is the rule to start with:
list_templates is read-only, so it stays allowed. 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 list_templates call is checked against it from then on.
Questions about list_templates
Список шаблонів: record, email, sms. Якщо kind не вказано — повертає всі типи. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
list_templates accepts 3 parameters: kind, app_id, entity_id. Required: 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 list_templates: 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.
list_templates is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_templates 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 list_templates. 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.
list_templates 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