list_action_rules
Повернути список всіх action-правил (тригерів автоматизації) форми.
This record as markdown: /tools/com-quintadb-mcp/list-action-rules.md
What list_action_rules does on QuintaDB
AI agents call list_action_rules to retrieve information from QuintaDB without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
app_id | string | Yes | ID проєкту |
entity_id | string | Yes | ID форми |
Parameters from the server's own tool schema.
Why list_action_rules is rated Low
This tool retrieves and enumerates automation rules without creating, modifying, deleting, or executing them. It is purely a data retrieval operation on form configuration metadata. The blast radius of misuse is minimal—exposure of rule definitions cannot directly cause harm, though it reveals automation logic. Classified as Read with low severity and high confidence.
From the tool's definition Tool name 'list_action_rules' and description 'Повернути список всіх action-правил (тригерів автоматизації) форми' indicates listing/retrieval of action rules (automation triggers).
Attacks that exploit this kind of access
The rule that runs list_action_rules 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 list_action_rules, this is the rule to start with:
list_action_rules is read-only, so it stays allowed. 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 list_action_rules call is checked against it from then on.
Questions about list_action_rules
Повернути список всіх action-правил (тригерів автоматизації) форми. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
list_action_rules accepts 2 parameters: app_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 list_action_rules: 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.
list_action_rules is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_action_rules 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 list_action_rules. 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.
list_action_rules 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