set_column_size
Змінити ширину колонки в таблиці або всередині субформи/linked_records. Використовуй коли юзер просить зробити колонку ширше/вужче, збільшити/зменшити розмір колонки у вигляді таблиці.
This record as markdown: /tools/com-quintadb-mcp/set-column-size.md
What set_column_size does on QuintaDB
AI agents use set_column_size 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 |
|---|---|---|---|
size | integer | Yes | Нова ширина в пікселях (наприклад 200) |
app_id | string | Yes | ID проєкту |
field_id | string | Yes | ID поля-колонки, ширину якої міняємо |
entity_id | string | Yes | ID форми, таблиця якої міняється |
subform_field_id | string | — | Якщо міняємо колонку ВСЕРЕДИНІ субформи або linked_records — передай сюди ID поля-субформи (linked_records/subform). Без цього параметра міняється колонка в осн |
Parameters from the server's own tool schema.
Why set_column_size is rated Medium
This tool changes UI/display properties (column width) within a table or subform, which is a reversible modification to the presentation layer. It does not create, delete, or execute external operations—it only adjusts metadata about how existing data is displayed. This is a Write action with low severity since the blast radius of misconfiguration is limited to visual layout and easily correctable.
From the tool's definition Tool name 'set_column_size' and description indicate it modifies table column width (змінити ширину колонки).
Attacks that exploit this kind of access
The rule that runs set_column_size 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 set_column_size, this is the rule to start with:
set_column_size 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 set_column_size call is checked against it from then on.
Questions about set_column_size
Змінити ширину колонки в таблиці або всередині субформи/linked_records. Використовуй коли юзер просить зробити колонку ширше/вужче, збільшити/зменшити розмір колонки у вигляді таблиці. 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.
set_column_size accepts 5 parameters: size, app_id, field_id, entity_id, subform_field_id. Required: size, app_id, field_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 set_column_size: 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.
set_column_size 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 set_column_size 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 set_column_size. 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.
set_column_size 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