update_report

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 122 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-quintadb-mcp/update-report.md

WHAT IT DOES

What update_report does on QuintaDB

AI agents use update_report 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
`asc`	boolean	—	true = ascending, false = descending
`app_id`	string	Yes	Project ID (from list_projects)
`sort_by`	string	—	Field id or name to sort the records by
`new_name`	string	—
`per_page`	integer	—	Number of records per page (max 100, default 20)
`criterias`	array	—	The report's filters, ALL of them: this list replaces the ones it has (an empty list removes every filter). Same shape as in create_report.
`report_id`	string	Yes	View/filter ID (from get_reports)
`property_ids`	array	—	The columns shown, ALL of them (field ids or names); an empty list shows every column
`total_by_group`	boolean	—	false removes the total; true goes with total_by_group_column_id
`group_field_ids`	array	—	The fields the records are grouped by, ALL of them (ids or names); an empty list removes the grouping
`average_by_group`	boolean	—	false removes the average; true goes with average_by_group_column_id
`only_groupname_and_count`	boolean	—	true = show only each group's name and how many records it holds

Parameters from the server's own tool schema.

RISK

Why update_report is rated Medium

An AI agent can call update_report faster than any human can review: one bad instruction and it creates or modifies resources in QuintaDB by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (21 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_report Rate-limited

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

FAQ

Questions about update_report

What does the update_report tool do? +

Change a report: its name, its filters, the columns it shows, how it is sorted, how many records a page holds. Pass only what changes. criterias REPLACES all the report's filters. group_field_ids REPLACES its grouping (798): an empty list makes it a plain list again; a total or an average needs a grouping. Ids come from get_reports. 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 update_report accept? +

update_report accepts 12 parameters: asc, app_id, sort_by, new_name, per_page, criterias, report_id, property_ids, total_by_group, group_field_ids, average_by_group, only_groupname_and_count. Required: app_id, report_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_report? +

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

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

Can I rate-limit update_report? +

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

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

update_report 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 150 QuintaDB tools →

Across the catalogue

generate_devtools_report on Percepta MCP Server →generate_forensic_report on Android Forensics ADB MCP Server →aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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