create_map
Створити карту Google Maps з джерелами даних (маркерами з форм). center_type: 1=адреса, 2=координати, 3=перший запис.
This record as markdown: /tools/com-quintadb-mcp/create-map.md
What create_map does on QuintaDB
AI agents use create_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 |
|---|---|---|---|
name | string | Yes | Display name |
app_id | string | Yes | Project ID (from list_projects) |
center_type | integer | — | 1=адреса, 2=координати, 3=перший запис |
data_sources | array | — | |
center_address | string | — | Адреса центру (для center_type=1) |
center_latitude | number | — | |
center_longitude | number | — |
Parameters from the server's own tool schema.
Why create_map is rated Medium
This tool creates a new map entity (Write category) rather than merely retrieving data. While it visualizes existing form data via markers, it creates a persistent map artifact that modifies the database/portal structure.
From the tool's definition Tool name 'create_map' and description indicate creation of a Google Maps visualization with data sources (markers from forms). The verb 'create' and the ability to add markers/data sources represents data creation and configuration modification.
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
The rule that runs create_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 create_map, this is the rule to start with:
create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every create_map call is checked against it from then on.
Questions about create_map
Створити карту Google Maps з джерелами даних (маркерами з форм). center_type: 1=адреса, 2=координати, 3=перший запис. 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.
create_map accepts 7 parameters: name, app_id, center_type, data_sources, center_address, center_latitude, center_longitude. Required: name, app_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 create_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.
create_map 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 create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
More on QuintaDB, and thousands of servers like it.
This server
Across the catalogue