update_action_rule
Оновити параметри існуючого action-правила (тригера) на формі.
This record as markdown: /tools/com-quintadb-mcp/update-action-rule.md
What update_action_rule does on QuintaDB
AI agents use update_action_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 |
|---|---|---|---|
name | string | — | Назва правила для пошуку (якщо action_id не передано) |
app_id | string | Yes | ID проєкту |
new_name | string | — | Нова назва правила |
settings | object | — | Хеш налаштувань для злиття з поточними (action_trigger, action_type, email_template_id тощо) |
action_id | string | — | ID action property (пріоритет) |
entity_id | string | Yes | ID форми |
Parameters from the server's own tool schema.
Why update_action_rule is rated Medium
This tool modifies existing automation rules/triggers in a no-code database system. While not destructive (the rule can be modified again), it is a Write operation that changes form behavior and automation logic. Severity is high because misconfigured automation rules could cause unintended data modifications, notifications, or workflow disruptions affecting multiple records or users.
From the tool's definition update_action_rule updates (modifies) parameters of an existing action-rule (trigger) on a form. The verb 'update' and 'оновити' (Ukrainian: update) indicate modification of configuration.
Attacks that exploit this kind of access
The rule that runs update_action_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 update_action_rule, this is the rule to start with:
update_action_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.
The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every update_action_rule call is checked against it from then on.
Questions about update_action_rule
Оновити параметри існуючого action-правила (тригера) на формі. It is categorised as a Write tool in the QuintaDB MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_action_rule accepts 6 parameters: name, app_id, new_name, settings, action_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 update_action_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.
update_action_rule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_action_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.
Set action: deny in the PolicyLayer policy for update_action_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.
update_action_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.
More on QuintaDB, and thousands of servers like it.
This server
Across the catalogue