create_calendar
Створити календар з джерелами даних (подіями з форм). date_title_type: 0=поле, 1=фіксований текст. info_window_type: 0=поле, 1=фіксований текст.
This record as markdown: /tools/com-quintadb-mcp/create-calendar.md
What create_calendar does on QuintaDB
AI agents use create_calendar 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 |
|---|---|---|---|
name | string | Yes | Display name |
app_id | string | Yes | Project ID (from list_projects) |
data_sources | array | — |
Parameters from the server's own tool schema.
Why create_calendar is rated Medium
This tool creates a new calendar artifact within the QuintaDB system, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. The blast radius is moderate because misconfiguration could create incorrect calendar structures or expose unintended data in event displays, but the action itself is non-destructive and can be undone.
From the tool's definition Tool name 'create_calendar' and description indicates creation of a new calendar resource with data sources (events from forms). The parameters for date_title_type and info_window_type show configuration options for how data is mapped and displayed.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs create_calendar 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_calendar, this is the rule to start with:
create_calendar 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_calendar call is checked against it from then on.
Questions about create_calendar
Створити календар з джерелами даних (подіями з форм). date_title_type: 0=поле, 1=фіксований текст. info_window_type: 0=поле, 1=фіксований текст. 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_calendar accepts 3 parameters: name, app_id, data_sources. Required: name, 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 create_calendar: 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_calendar 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_calendar 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_calendar. 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_calendar 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