update_reminder

Change a reminder that exists: the date field, how many days before, the time, the time zone, who gets it, whether it repeats.

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 82 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-reminder.md

WHAT IT DOES

What update_reminder does on QuintaDB

AI agents use update_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)
`repeat`	string	—	every_day \| every_week \| every_month \| every_year, or "" for once
`run_time`	string	—	HH:MM, 24 hours
`time_zone`	string	—	e.g. UTC+02
`date_field`	string	—	The date field's name or id
`recipients`	array	—	The whole list of email addresses; an empty list = the record's owner
`days_before`	integer	—	0 = on the day, negative = after it
`reminder_id`	string	Yes	From list_reminders

Parameters from the server's own tool schema.

RISK

Why update_reminder is rated Medium

An AI agent can call update_reminder 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_reminder Rate-limited

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

View as policy code

policy.json

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

FAQ

Questions about update_reminder

What does the update_reminder tool do? +

Change a reminder that exists: the date field, how many days before, the time, the time zone, who gets it, whether it repeats. 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.

What parameters does update_reminder accept? +

update_reminder accepts 8 parameters: app_id, repeat, run_time, time_zone, date_field, recipients, days_before, reminder_id. Required: app_id, reminder_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_reminder? +

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

What risk level is update_reminder? +

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

Can I rate-limit update_reminder? +

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

How do I block update_reminder completely? +

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

What MCP server provides update_reminder? +

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

KEEP EXPLORING

More on QuintaDB, and thousands of servers like it.

This server

All 150 QuintaDB tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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