# set_field_visibility_rule Показати або сховати поля форми залежно від значення іншого поля (умовні поля). Наприклад: коли «Статус» = «в процесі» — відкрити «Чого бракує» і «Коли передзвонити». Діє і у внутрішній формі, і в публічній. Agent View of the PolicyLayer registry record for `set_field_visibility_rule`. HTML page: https://policylayer.com/tools/com-quintadb-mcp/set-field-visibility-rule ## Facts - Tool: `set_field_visibility_rule` - Server: QuintaDB (`https://quintadb.com/mcp`) — https://policylayer.com/tools/com-quintadb-mcp.md - Homepage: https://github.com/https://quintadb.com/mcp - Risk category: Write (Medium risk) - Registry record: grade F, identity unverified - Server auth posture: open - Server rate-limited: no - Parameters: 7 (4 required) - Recommended policy verdict: Rate-limited ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `app_id` | string | yes | Project ID (from list_projects) | | `condition` | string | no | Оператор умови; типово «is» (дорівнює). Інші: is_not, contains, not_contains, starts_with, ends_with, is_empty, is_not_empty, greater_than, less_than, before, a | | `entity_id` | string | yes | Form ID (from list_forms or describe_project) | | `when_value` | string | yes | Значення, при якому правило спрацьовує — рівно як воно записане в опціях поля | | `when_field_id` | string | yes | ID поля-умови (напр. поле статусу) | | `hide_field_ids` | array | no | ID полів, які СХОВАТИ. Разом із show_field_ids не передавати. | | `show_field_ids` | array | no | ID полів, які ПОКАЗАТИ | Parameters from the server's own tool schema. ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "set_field_visibility_rule", "arguments": { "app_id": "", "entity_id": "", "when_value": "", "when_field_id": "" } } } ``` ## Why set_field_visibility_rule is rated Medium An AI agent can call set_field_visibility_rule 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. ## Use case AI agents use set_field_visibility_rule 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. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches QuintaDB: ```json { "version": "1", "default": "deny", "tools": { "set_field_visibility_rule": { "limits": [ { "counter": "set_field_visibility_rule_rate", "window": "minute", "max": 30, "scope": "grant" } ] } } } ``` ## Other tools on QuintaDB (149) - `delete_action_rule` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-action-rule.md - `delete_calendar` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-calendar.md - `delete_chart` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-chart.md - `delete_dashboard_item` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-dashboard-item.md - `delete_few_records` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-few-records.md - `delete_field` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-field.md - `delete_form` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-form.md - `delete_formatting` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-formatting.md - `delete_map` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-map.md - `delete_portal` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-portal.md - `delete_portal_group` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-portal-group.md - `delete_portal_menu_item` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-portal-menu-item.md - `delete_portal_page` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-portal-page.md - `delete_portal_user` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-portal-user.md - `delete_project` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-project.md - `delete_record` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-record.md - `delete_records_by_filter` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-records-by-filter.md - `delete_reminder` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-reminder.md - `delete_report` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-report.md - `delete_saved_view` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-saved-view.md - `delete_schedule` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-schedule.md - `delete_team_group` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-team-group.md - `delete_template` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-template.md - `delete_webhook` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/delete-webhook.md - `remove_example_records` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/remove-example-records.md - `remove_user_from_portal_group` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/remove-user-from-portal-group.md - `remove_user_from_team_group` — Destructive — https://policylayer.com/tools/com-quintadb-mcp/remove-user-from-team-group.md - `run_action` — Execute — https://policylayer.com/tools/com-quintadb-mcp/run-action.md - `check_ai_site_status` — Read — https://policylayer.com/tools/com-quintadb-mcp/check-ai-site-status.md - `describe_project` — Read — https://policylayer.com/tools/com-quintadb-mcp/describe-project.md - …and 119 more: https://policylayer.com/tools/com-quintadb-mcp.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-quintadb-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-quintadb-mcp