create_schedule

Створити розклад автоматичної розсилки записів форми на email (daily/weekly/monthly).

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 92 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-quintadb-mcp/create-schedule.md

WHAT IT DOES

What create_schedule does on QuintaDB

AI agents use create_schedule 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)
`period`	string	—	daily, weekly, monthly
`run_time`	string	—	Час запуску HH:MM (default: 08:00)
`entity_id`	string	Yes	Form ID (from list_forms or describe_project)
`report_id`	string	—	ID звіту для відправки з фільтром
`time_zone`	string	—
`recipients`	array	—	Масив email-адрес
`export_type`	string	—	email (default), ftp, sftp
`email_template_id`	string	—

Parameters from the server's own tool schema.

RISK

Why create_schedule is rated Medium

The tool creates a new scheduling rule for automated email delivery of form records. This is a Write operation because it creates/configures new data structures (the schedule itself) and modifies system automation state reversibly. It is not Destructive (schedules can be deleted/modified), not Execute (does not run arbitrary code or trigger external systems beyond a predefined automation), and not Financial.

From the tool's definition Tool creates/configures automated email distribution schedules ('create_schedule' paired with 'розсилки записів' — dispatch of records). This is a reversible configuration action that modifies system state.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

create_schedule Rate-limited

create_schedule 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": {
    "create_schedule": {
      "limits": [
        {
          "counter": "create_schedule_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 create_schedule call is checked against it from then on.

FAQ

Questions about create_schedule

What does the create_schedule tool do? +

Створити розклад автоматичної розсилки записів форми на email (daily/weekly/monthly). 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 create_schedule accept? +

create_schedule accepts 9 parameters: app_id, period, run_time, entity_id, report_id, time_zone, recipients, export_type, email_template_id. Required: app_id, entity_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_schedule? +

Register the QuintaDB MCP server in PolicyLayer and add a rule for create_schedule: 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 create_schedule? +

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

Can I rate-limit create_schedule? +

Yes. Add a rate_limit block to the create_schedule 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 create_schedule completely? +

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

create_schedule 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 116 QuintaDB tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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