get_field_types
Повний довідник типів полів QuintaDB з описами параметрів. Виклич перед create_field якщо потрібна формула, linked_column, rel, або будь-який нестандартний тип. Повертає всі 40+ типів та детальну специфікацію формул з правилами Ruby-скриптів і прикладами.
This record as markdown: /tools/com-quintadb-mcp/get-field-types.md
What get_field_types does on QuintaDB
AI agents call get_field_types 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 |
|---|---|---|---|
field_type | string | — | One field type (as create_field names it): the answer is the settings that type takes — what each sets and the value it takes — to pass as settings: {…} to crea |
Parameters from the server's own tool schema.
Why get_field_types is rated Low
This tool retrieves and queries reference information about field types and their specifications. It is informational only, with no side effects on data or system state. Users call it to get documentation before creating fields, making it a pure Read operation with minimal risk.
From the tool's definition Tool returns reference documentation: 'Повний довідник типів полів' (Complete reference guide of field types), 'Повертає всі 40+ типи' (Returns all 40+ types). No modification, deletion, or execution of operations.
Attacks that exploit this kind of access
The rule that runs get_field_types 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_field_types, this is the rule to start with:
get_field_types 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_field_types call is checked against it from then on.
Questions about get_field_types
Повний довідник типів полів QuintaDB з описами параметрів. Виклич перед create_field якщо потрібна формула, linked_column, rel, або будь-який нестандартний тип. Повертає всі 40+ типів та детальну специфікацію формул з правилами Ruby-скриптів і прикладами. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
get_field_types accepts 1 parameter: field_type. 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_field_types: 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_field_types 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_field_types 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_field_types. 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_field_types 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