get_form_fields
Отримати поля форми з назвами та типами. ОБОВ'ЯЗКОВО викликай перед create_record та створенням розсилок, щоб знати точні назви та html_name полів
This record as markdown: /tools/com-quintadb-mcp/get-form-fields.md
What get_form_fields does on QuintaDB
AI agents call get_form_fields 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) |
entity_id | string | Yes | ID форми з list_forms |
Parameters from the server's own tool schema.
Why get_form_fields is rated Low
This tool retrieves metadata about form structure (field names and types) without modifying, deleting, or executing operations. It is a read-only query that returns information to inform subsequent operations. The low severity reflects minimal blast radius—knowing form field names causes no direct harm, though it could inform targeted data exfiltration if combined with other tools.
From the tool's definition Tool name 'get_form_fields' and description 'Отримати поля форми' (Get form fields) with 'назвами та типами' (names and types).
Attacks that exploit this kind of access
The rule that runs get_form_fields 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_form_fields, this is the rule to start with:
get_form_fields 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_form_fields call is checked against it from then on.
Questions about get_form_fields
Отримати поля форми з назвами та типами. ОБОВ'ЯЗКОВО викликай перед create_record та створенням розсилок, щоб знати точні назви та html_name полів. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
get_form_fields accepts 2 parameters: app_id, entity_id. Required: app_id, entity_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_form_fields: 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_form_fields 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_form_fields 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_form_fields. 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_form_fields 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