run_action
Запустити автоматизацію (action rule) для запису — відправити email, тригер webhook тощо. action_id — ID поля-кнопки дії
This record as markdown: /tools/com-quintadb-mcp/run-action.md
What run_action does on QuintaDB
AI agents invoke run_action to trigger actions in QuintaDB. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
action_id | string | Yes | ID поля типу 'action' (кнопка автоматизації) |
record_id | string | Yes | ID запису для якого запускається дія |
Parameters from the server's own tool schema.
Why run_action is rated High
This tool executes automation rules that can have side effects outside the database system (sending emails, triggering webhooks). While not destructive to data itself, it initiates external operations that could affect systems, users, or business logic. Misuse could spam users, trigger unwanted integrations, or execute malicious webhook calls.
From the tool's definition Tool description states it 'runs automation (action rule) for a record — send email, trigger webhook etc.' The phrasing 'запустити автоматизацію' (run automation) combined with capability to trigger webhooks and send emails indicates execution of external…
Attacks that exploit this kind of access
The rule that runs run_action 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 run_action, this is the rule to start with:
run_action stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 run_action call is checked against it from then on.
Questions about run_action
Запустити автоматизацію (action rule) для запису — відправити email, тригер webhook тощо. action_id — ID поля-кнопки дії. It is categorised as a Execute tool in the QuintaDB MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
run_action accepts 2 parameters: action_id, record_id. Required: action_id, record_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 run_action: 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.
run_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_action 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 run_action. 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.
run_action 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.
Across the catalogue