create_reminder
Створити нагадування: надіслати email за N днів до/після значення поля дати.
This record as markdown: /tools/com-quintadb-mcp/create-reminder.md
What create_reminder does on QuintaDB
AI agents use create_reminder 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 |
|---|---|---|---|
app_id | string | Yes | Project ID (from list_projects) |
run_time | string | — | Час HH:MM (default: 08:00) |
entity_id | string | Yes | Form ID (from list_forms or describe_project) |
time_zone | string | — | |
date_field | string | Yes | Назва або ID поля дати |
recipients | array | — | Email-адреси |
days_before | integer | — | За скільки днів до дати (0 = в день події, від'ємне = після) |
email_template_id | string | — |
Parameters from the server's own tool schema.
Why create_reminder is rated Medium
This tool creates new reminder automation rules that will trigger email notifications. It is a Write operation because it irreversibly adds new data/configuration to the system. Severity is medium because a misconfigured reminder could spam users with unwanted emails, but the blast radius is limited to notification delivery rather than data loss or financial impact.
From the tool's definition Tool creates a reminder to send email at a future date based on a field value. The description indicates it 'creates' (Створити) a reminder, which modifies the system state by adding a new automation rule.
Attacks that exploit this kind of access
The rule that runs create_reminder 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_reminder, this is the rule to start with:
create_reminder 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_reminder call is checked against it from then on.
Questions about create_reminder
Створити нагадування: надіслати email за N днів до/після значення поля дати. 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_reminder accepts 8 parameters: app_id, run_time, entity_id, time_zone, date_field, recipients, days_before, email_template_id. Required: app_id, entity_id, date_field. 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_reminder: 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_reminder 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_reminder 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_reminder. 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_reminder 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