This record as markdown: /tools/com-quintadb-mcp/list-reminders.md
What list_reminders does on QuintaDB
AI agents call list_reminders 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 |
|---|---|---|---|
app_id | string | Yes | Project ID (from list_projects) |
entity_id | string | — | Form ID (from list_forms or describe_project) |
Parameters from the server's own tool schema.
Why list_reminders is rated Low
This tool retrieves or queries reminder data based on date fields. It exhibits the classic Read operation pattern: listing/fetching existing data without side effects. No creation, modification, deletion, or code execution occurs.
From the tool's definition Tool name 'list_reminders' and description 'Список нагадувань по даті поля' (Ukrainian: 'List of reminders by date field') indicate data retrieval functionality with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs list_reminders 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_reminders, this is the rule to start with:
list_reminders 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_reminders call is checked against it from then on.
Questions about list_reminders
Список нагадувань по даті поля. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
list_reminders accepts 2 parameters: 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_reminders: 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_reminders 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_reminders 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_reminders. 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_reminders 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