upload_file_to_record

Завантажити файл або зображення до поля запису. Приймає вміст файлу в base64. Зберігає файл і прикріплює до вказаного поля. Для multiple-файлових полів додає до існуючих.

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 66 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-quintadb-mcp/upload-file-to-record.md

WHAT IT DOES

What upload_file_to_record does on QuintaDB

AI agents use upload_file_to_record 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)
`entity_id`	string	Yes	Form ID (from list_forms or describe_project)
`file_name`	string	Yes	Ім'я файлу з розширенням, наприклад 'invoice.pdf' або 'photo.jpg'
`record_id`	string	Yes	ID запису до якого прикріпити файл
`field_name`	string	Yes	Назва або ID файлового/зображення поля
`file_content`	string	Yes	Вміст файлу закодований у base64

Parameters from the server's own tool schema.

RISK

Why upload_file_to_record is rated Medium

This tool creates and modifies data within records by attaching files. It is clearly a Write operation because it adds or modifies record attachments. The severity is medium because: (1) the action is reversible (files can be deleted), (2) blast radius is limited to the target record and its attachments, (3) no data deletion or financial impact occurs.

From the tool's definition Uploads and attaches files to records, modifying record data. Description states 'Завантажити файл...Зберігає файл і прикріплює до вказаного поля' (Upload file...Saves file and attaches to specified field).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

upload_file_to_record Rate-limited

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

FAQ

Questions about upload_file_to_record

What does the upload_file_to_record tool do? +

Завантажити файл або зображення до поля запису. Приймає вміст файлу в base64. Зберігає файл і прикріплює до вказаного поля. Для multiple-файлових полів додає до існуючих. 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 upload_file_to_record accept? +

upload_file_to_record accepts 6 parameters: app_id, entity_id, file_name, record_id, field_name, file_content. Required: app_id, entity_id, file_name, record_id, field_name, file_content. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on upload_file_to_record? +

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

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

Can I rate-limit upload_file_to_record? +

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

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

upload_file_to_record 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

aroflo_create_or_update_record on AroFlo MCP →team_manager_record_checkpoint on Team Manager MCP → The MCP Attack Database →

Guides

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