update_map

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 102 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-map.md

WHAT IT DOES

What update_map does on QuintaDB

AI agents use update_map 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
`zoom`	integer	—
`app_id`	string	Yes	Project ID (from list_projects)
`map_id`	string	Yes
`new_name`	string	—
`center_type`	integer	—	1 = an address, 2 = coordinates, 3 = the first record
`center_address`	string	—
`center_latitude`	number	—
`add_data_sources`	array	—	Sources of markers to ADD to the ones the map has. Each needs address_field_id, or latitude_field_id with longitude_field_id.
`center_longitude`	number	—
`remove_data_source_ids`	array	—	Ids of the sources to remove, from list_maps

Parameters from the server's own tool schema.

RISK

Why update_map is rated Medium

An AI agent can call update_map 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) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_map Rate-limited

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

FAQ

Questions about update_map

What does the update_map tool do? +

Change a map: its name, where it is centred (center_type 1 = an address, 2 = coordinates, 3 = the first record) and its zoom. Pass only what changes. add_data_sources adds sources of markers and remove_data_source_ids removes sources by the ids list_maps shows (798); every other source stays as it is. Ids come from list_maps. 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_map accept? +

update_map accepts 10 parameters: zoom, app_id, map_id, new_name, center_type, center_address, center_latitude, add_data_sources, center_longitude, remove_data_source_ids. Required: app_id, map_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_map? +

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

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

Can I rate-limit update_map? +

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

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

update_map 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

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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