get_rel_id
Отримати numeric rel_id для поля типу 'rel' (зв'язок). Потрібен перед create/update record якщо треба заповнити rel-поле. Передай entity_id форми і property_id поля-зв'язку.
This record as markdown: /tools/com-quintadb-mcp/get-rel-id.md
What get_rel_id does on QuintaDB
AI agents call get_rel_id 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 |
|---|---|---|---|
entity_id | string | Yes | ID форми де знаходиться rel-поле |
property_id | string | Yes | ID поля типу rel (з get_form_fields) |
Parameters from the server's own tool schema.
Why get_rel_id is rated Low
This tool retrieves metadata (a numeric relationship ID) from the database based on form entity_id and field property_id parameters. It is a lookup/query operation with no side effects, fitting the Read category. The low severity reflects that obtaining a relationship identifier poses minimal risk—it cannot modify data, execute code, or cause destructive changes.
From the tool's definition Tool description indicates it 'Отримати numeric rel_id' (retrieves numeric rel_id) for a relationship field type. It fetches/queries a relationship identifier needed before creating or updating records.
Attacks that exploit this kind of access
The rule that runs get_rel_id 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_rel_id, this is the rule to start with:
get_rel_id is read-only, so it stays allowed. 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 get_rel_id call is checked against it from then on.
Questions about get_rel_id
Отримати numeric rel_id для поля типу 'rel' (зв'язок). Потрібен перед create/update record якщо треба заповнити rel-поле. Передай entity_id форми і property_id поля-зв'язку. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
get_rel_id accepts 2 parameters: entity_id, property_id. Required: entity_id, property_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 get_rel_id: 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.
get_rel_id is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_rel_id 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 get_rel_id. 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.
get_rel_id 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