create_schedule
Mail a table's or a report's rows as a file on a schedule: every day or on one weekday, at a time, to the listed addresses.
This record as markdown: /tools/com-quintadb-mcp/create-schedule.md
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 |
|---|---|---|---|
day | string | — | Monday … Sunday, or Daily (default) |
name | string | — | The file's name (default: the table's name) |
app_id | string | Yes | Project ID (from list_projects) |
run_time | string | — | HH:MM, 24 hours (default 08:00) |
entity_id | string | Yes | Form ID (from list_forms or describe_project) |
file_type | string | — | xls (default) | csv |
report_id | string | — | A report of this table — only its rows are sent |
time_zone | string | — | e.g. UTC+02 |
recipients | array | Yes | Email addresses the file is mailed to |
Parameters from the server's own tool schema.
Why create_schedule is rated Medium
An AI agent can call create_schedule 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
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 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_schedule call is checked against it from then on.
Questions about create_schedule
Mail a table's or a report's rows as a file on a schedule: every day or on one weekday, at a time, to the listed addresses. 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_schedule accepts 9 parameters: day, name, app_id, run_time, entity_id, file_type, report_id, time_zone, recipients. Required: app_id, entity_id, recipients. 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_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.
create_schedule 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_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.
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.
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.
More on QuintaDB, and thousands of servers like it.
This server
Across the catalogue