get_relationship

Показати, як налаштований звʼязок поля з іншою таблицею: тип (список / радіо / автокомпліт / чекбокси), яку колонку показуємо замість id, колонка звʼязку. Позначає недороблені звʼязки.

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Low RISK CLASS

Category Read

Parameters 33 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-quintadb-mcp/get-relationship.md

WHAT IT DOES

What get_relationship does on QuintaDB

AI agents call get_relationship 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)
`field_id`	string	Yes	ID поля типу «звʼязок»
`entity_id`	string	Yes	Form ID (from list_forms or describe_project)

Parameters from the server's own tool schema.

RISK

Why get_relationship is rated Low

Even though get_relationship only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_relationship Allowed

get_relationship is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_relationship": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every get_relationship call is checked against it from then on.

FAQ

Questions about get_relationship

What does the get_relationship tool do? +

What parameters does get_relationship accept? +

get_relationship accepts 3 parameters: app_id, field_id, entity_id. Required: app_id, field_id, entity_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_relationship? +

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

get_relationship is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_relationship? +

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

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

get_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

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →