update_relationship

Полагодити або змінити звʼязок: тип відображення (rel_code) і колонку, яку показувати замість id. Коди: 0 має багато, 1 багато-до-багатьох (автокомпліт), 2 належить (випадаючий список), 3 має один, 4 багато-до-багатьох (чекбокси), 5 має один (радіо), 6 належить (радіо), 8 належить (автокомпліт), ...

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 53 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-relationship.md

WHAT IT DOES

What update_relationship does on QuintaDB

AI agents use update_relationship 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
`app_id`	string	Yes	Project ID (from list_projects)
`rel_code`	integer	—	Новий тип звʼязку
`entity_id`	string	Yes	Form ID (from list_forms or describe_project)
`show_column_id`	string	—	ID поля в цільовій таблиці, яке показувати людині
`relationship_id`	integer	Yes	ID звʼязку з get_relationship

Parameters from the server's own tool schema.

RISK

Why update_relationship is rated Medium

An AI agent can call update_relationship 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_relationship Rate-limited

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

FAQ

Questions about update_relationship

What does the update_relationship tool do? +

What parameters does update_relationship accept? +

update_relationship accepts 5 parameters: app_id, rel_code, entity_id, show_column_id, relationship_id. Required: app_id, entity_id, relationship_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_relationship? +

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

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

Can I rate-limit update_relationship? +

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

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

update_relationship 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 →