delete_action_rule
Remove an automation (an action rule) from a table. Cannot be undone. Ids come from list_action_rules.
This record as markdown: /tools/com-quintadb-mcp/delete-action-rule.md
What delete_action_rule does on QuintaDB
AI agents call delete_action_rule to permanently remove resources in QuintaDB, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
app_id | string | Yes | Project ID (from list_projects) |
action_id | string | Yes | The rule id from list_action_rules, as a string |
entity_id | string | Yes | Form ID (from list_forms or describe_project) |
Parameters from the server's own tool schema.
Why delete_action_rule is rated Critical
An AI agent that decides to call delete_action_rule doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from QuintaDB is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_action_rule, this is the rule to start with:
delete_action_rule is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every delete_action_rule call is checked against it from then on.
Questions about delete_action_rule
Remove an automation (an action rule) from a table. Cannot be undone. Ids come from list_action_rules. It is categorised as a Destructive tool in the QuintaDB MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_action_rule accepts 3 parameters: app_id, action_id, entity_id. Required: app_id, action_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 delete_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.
delete_action_rule is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue