set_field_visibility_rule

Показати або сховати поля форми залежно від значення іншого поля (умовні поля). Наприклад: коли «Статус» = «в процесі» — відкрити «Чого бракує» і «Коли передзвонити». Діє і у внутрішній формі, і в публічній.

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 74 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-quintadb-mcp/set-field-visibility-rule.md

WHAT IT DOES

What set_field_visibility_rule does on QuintaDB

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.

Parameter	Type	Required	Description
`app_id`	string	Yes	Project ID (from list_projects)
`condition`	string	—	Оператор умови; типово «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	—	ID полів, які СХОВАТИ. Разом із show_field_ids не передавати.
`show_field_ids`	array	—	ID полів, які ПОКАЗАТИ

Parameters from the server's own tool schema.

RISK

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

set_field_visibility_rule Rate-limited

set_field_visibility_rule stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_field_visibility_rule": {
      "limits": [
        {
          "counter": "set_field_visibility_rule_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about set_field_visibility_rule

What does the set_field_visibility_rule tool do? +

What parameters does set_field_visibility_rule accept? +

set_field_visibility_rule accepts 7 parameters: app_id, condition, entity_id, when_value, when_field_id, hide_field_ids, show_field_ids. Required: app_id, entity_id, when_value, when_field_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_field_visibility_rule? +

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

set_field_visibility_rule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_field_visibility_rule? +

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

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

set_field_visibility_rule 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

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →