attach_media_to_record
Прикріпити файл із бібліотеки MyFile до поля типу file або image конкретного запису. Використовуй для attached_files замість update_record, якщо поле має тип file/image.
This record as markdown: /tools/com-quintadb-mcp/attach-media-to-record.md
What attach_media_to_record does on QuintaDB
AI agents use attach_media_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) |
field_id | string | Yes | ID поля типу file або image |
entity_id | string | Yes | ID форми |
record_id | string | Yes | ID запису |
my_file_id | string | Yes | media_id прикріпленого MyFile |
Parameters from the server's own tool schema.
Why attach_media_to_record is rated Medium
This is a Write operation because it creates or modifies data reversibly—attaching a media file to a record. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), and does not involve financial transactions (not Financial).
From the tool's definition Tool name 'attach_media_to_record' and description indicate it attaches/adds a file to a record's file or image field.
Attacks that exploit this kind of access
The rule that runs attach_media_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 attach_media_to_record, this is the rule to start with:
attach_media_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.
The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every attach_media_to_record call is checked against it from then on.
Questions about attach_media_to_record
Прикріпити файл із бібліотеки MyFile до поля типу file або image конкретного запису. Використовуй для attached_files замість update_record, якщо поле має тип file/image. 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.
attach_media_to_record accepts 5 parameters: app_id, field_id, entity_id, record_id, my_file_id. Required: app_id, field_id, entity_id, record_id, my_file_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 attach_media_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.
attach_media_to_record 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 attach_media_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.
Set action: deny in the PolicyLayer policy for attach_media_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.
attach_media_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.
More on QuintaDB, and thousands of servers like it.
This server
Across the catalogue