export_records
Експортувати записи форми у XLSX або PDF і надіслати на email.
This record as markdown: /tools/com-quintadb-mcp/export-records.md
What export_records does on QuintaDB
AI agents call export_records 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 |
|---|---|---|---|
email | string | — | Email отримувача (за замовчуванням — поточний юзер) |
app_id | string | Yes | Project ID (from list_projects) |
format | string | — | xlsx (default) або pdf |
entity_id | string | Yes | Form ID (from list_forms or describe_project) |
report_id | string | — | ID звіту/фільтру для вибіркового експорту |
Parameters from the server's own tool schema.
Why export_records is rated Low
The tool reads/exports records from a form into XLSX or PDF format. While it sends data to an email address (an external side effect), the primary action is data retrieval/export with no modification or deletion. The email delivery raises severity to medium due to potential data exfiltration risk if misused by an AI agent sending sensitive records to unintended recipients.
From the tool's definition Експортувати записи форми у XLSX або PDF і надіслати на email — 'export' and 'send to email' indicate reading/retrieving data and delivering it externally
Attacks that exploit this kind of access
The rule that runs export_records 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 export_records, this is the rule to start with:
export_records 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 export_records call is checked against it from then on.
Questions about export_records
Експортувати записи форми у XLSX або PDF і надіслати на email. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
export_records accepts 5 parameters: email, app_id, format, entity_id, report_id. Required: app_id, entity_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 export_records: 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.
export_records 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 export_records 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 export_records. 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.
export_records 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