get_column_total
Отримати суму або агрегат по числовому полю форми
This record as markdown: /tools/com-quintadb-mcp/get-column-total.md
What get_column_total does on QuintaDB
AI agents call get_column_total 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 |
|---|---|---|---|
app_id | string | Yes | Project ID (from list_projects) |
entity_id | string | Yes | Form ID (from list_forms or describe_project) |
report_id | string | — | Необов'язково: обмежити до конкретного звіту |
field_name | string | Yes | Назва числового поля |
Parameters from the server's own tool schema.
Why get_column_total is rated Low
This tool queries and calculates aggregates (sum, totals) over numeric form fields without creating, modifying, deleting, or executing external operations. It is a read-only analytic operation with minimal security impact.
From the tool's definition Tool name 'get_column_total' and description 'Отримати суму або агрегат по числовому полю форми' (Get sum or aggregate by numeric field of form) indicate a retrieval/aggregation operation with no data modification.
Attacks that exploit this kind of access
The rule that runs get_column_total 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 get_column_total, this is the rule to start with:
get_column_total 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 get_column_total call is checked against it from then on.
Questions about get_column_total
Отримати суму або агрегат по числовому полю форми. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
get_column_total accepts 4 parameters: app_id, entity_id, report_id, field_name. Required: app_id, entity_id, field_name. 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 get_column_total: 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.
get_column_total 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 get_column_total 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 get_column_total. 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.
get_column_total 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