list_schedules
Список розкладів автоматичного відправлення даних (email/ftp).
This record as markdown: /tools/com-quintadb-mcp/list-schedules.md
What list_schedules does on QuintaDB
AI agents call list_schedules 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_schedules is rated Low
This tool queries and retrieves existing automation schedules (email/FTP sending configurations). It performs data retrieval only, has no side effects, and does not modify, delete, or execute any operations. The blast radius of misuse is minimal—an agent could only view schedule information, not alter or trigger actions.
From the tool's definition Tool name 'list_schedules' and description indicating it retrieves/lists 'Список розкладів' (list of schedules) for automatic data sending. The verb 'list' is a read operation with no modification capability.
Attacks that exploit this kind of access
The rule that runs list_schedules 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_schedules, this is the rule to start with:
list_schedules 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_schedules call is checked against it from then on.
Questions about list_schedules
Список розкладів автоматичного відправлення даних (email/ftp). It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
list_schedules 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_schedules: 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_schedules 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_schedules 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_schedules. 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_schedules 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