DecisionRules
Create, manage, and test business rules directly from your AI agent via the DecisionRules platform.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data
What it can do
- Get Latest Rule: DecisionRules Management API tool for the authenticated space. Use when the user asks for the current/latest version of a rule and provides a rule ID or rule alias. Do not use this fo
- Update Latest Rule: DecisionRules Management API tool for the authenticated space. Persistence-only operation for replacing the latest rule version with an already complete DecisionRules payload. Do n
- Delete Latest Rule: DecisionRules Management API tool for the authenticated space. Use when the user explicitly wants to delete the current/latest version of a rule by rule ID or alias. This deletes t
What data it sees
Do you need an account
No: the server works without sign-in
Create, manage, and test business rules directly from your AI agent via the DecisionRules platform.
Server tool list (60)
Raw names from tools/list. Only developers need these.
| get_latest_rule | DecisionRules Management API tool for the authenticated space. Use when the user asks for the current/latest version of a rule and provides a rule ID or rule alias. Do not use this for folder paths; use get_rule_by_path when the user provides a path such as /Client/Important/Calculation. Returns the highest version regardless of publication status. |
| update_latest_rule | DecisionRules Management API tool for the authenticated space. Persistence-only operation for replacing the latest rule version with an already complete DecisionRules payload. Do not translate natural language, invent rule structure, or repair generated content with this tool; call propose_rule_edit and pass its complete proposal unchanged. To update a known version, use update_rule_version. |
| delete_latest_rule | DecisionRules Management API tool for the authenticated space. Use when the user explicitly wants to delete the current/latest version of a rule by rule ID or alias. This deletes the highest version regardless of publication status. Use delete_rule_version when the user gives a version, and delete_rule_by_path when the user gives a folder path. |
| get_rule_version | DecisionRules Management API tool for the authenticated space. Use when the user asks for a specific rule version and provides a rule ID or rule alias plus a version number. Returns that exact version regardless of publication status. Do not use for folder paths; use get_rule_by_path with the version query parameter instead. |
| update_rule_version | DecisionRules Management API tool for the authenticated space. Persistence-only operation for replacing one exact rule version with an already complete DecisionRules payload. Use this for an unpublished version that should be corrected in place. For a published rule whose history must be preserved, use create_rule_version instead. Do not translate natural language, merge partial edits, or repair rule structure here; call propose_rule_edit and pass its complete proposal unchanged. |
| delete_rule_version | DecisionRules Management API tool for the authenticated space. Use when the user explicitly wants to delete one exact rule version and provides a rule ID or rule alias plus a version number. Use delete_latest_rule only when no version is specified. |
| update_rule_version_status | DecisionRules Management API tool for the authenticated space. Use when the user wants to change the status of one exact rule version by rule ID or alias. The status path parameter must be either "pending" or "published"; version is required. |
| get_rule_by_path | DecisionRules Management API tool for the authenticated space. Use when the user provides a folder path to a rule instead of a rule ID or alias. The path must start with "/" and use folder names plus the rule name, not rule aliases or IDs, for example /Client/Important/Calculation. Add version only when selecting a specific rule version at that path. Returns the complete stored rule payload; use get_folder_tree_by_path when only folder-tree placement metadata is needed. |
| create_rule | DecisionRules Management API tool for the authenticated space. Persistence-only operation for saving a genuinely new DecisionRules resource. Do not use this tool to correct or replace an existing rule: preserve that rule's identity with propose_rule_edit followed by update_rule_version for an unpublished version or create_rule_version for a published rule. For natural-language authoring, first call the matching AIA generator and pass its `result.value` here unchanged. Do not invent, translate, or repair DecisionRules payload structure with this tool. |
| update_rule_by_path | DecisionRules Management API tool for the authenticated space. Persistence-only operation for replacing a rule identified by folder path with an already complete payload. The path must start with "/" and use folder names plus the rule name. Do not translate natural language or repair rule structure here; use propose_rule_edit first and pass its complete proposal unchanged. |
| delete_rule_by_path | DecisionRules Management API tool for the authenticated space. Use when the user wants to delete a rule identified by folder path instead of ID or alias. The path must start with "/" and use folder names plus the rule name, not rule aliases or IDs, for example /Client/Important/Calculation. Add version only when deleting a specific rule version at that path. |
| create_rule_version | DecisionRules Management API tool for the authenticated space. Persistence-only operation for adding a version from an already complete DecisionRules payload. This is the preferred way to correct a published rule because it preserves the existing alias and version history instead of creating a duplicate base rule. Use propose_rule_edit for natural-language changes, then pass its complete proposal unchanged. If the corrected rule belongs to a workflow you are maintaining, update that workflow's pinned rule version and rerun its scenarios; do not change unrelated workflows. |
| set_rule_lock_by_path | DecisionRules Management API tool for the authenticated space. Use when the user wants to lock or unlock a rule identified by folder path instead of ID or alias. The path must start with "/" and use folder names plus the rule name, not rule aliases or IDs, for example /Client/Important/Calculation. Add version only when locking or unlocking a specific rule version at that path. Body must be { "locked": true } or { "locked": false }. |
| set_latest_rule_lock | DecisionRules Management API tool for the authenticated space. Use when the user wants to lock or unlock the current/latest version of a rule by rule ID or alias. Body must be { "locked": true } or { "locked": false }. Use set_rule_version_lock when a version is provided, or set_rule_lock_by_path when the user gives a folder path. |
| set_rule_version_lock | DecisionRules Management API tool for the authenticated space. Use when the user wants to lock or unlock one exact rule version by rule ID or alias plus version number. Body must be { "locked": true } or { "locked": false }. |
| list_space_items | DecisionRules Management API tool for the authenticated space. Use when the user wants an inventory of rules and rule flows in the authenticated space. Returns item metadata such as baseId, version, name, status, type, tags, description, lastUpdate, and rule-flow dependency references. Use this to discover IDs or versions before calling more specific tools. |
| list_items_by_tags | DecisionRules Management API tool for the authenticated space. Use when the user wants to find rules or rule flows in the authenticated space by tags. Provide tags as a comma-separated query string such as "production,pricing"; returned items must match the supplied tags. |
| add_tags_to_item | DecisionRules Management API tool for the authenticated space. Use when the user wants to add tags to every version of a rule or rule flow identified by ID or alias. The body must be an array of tag objects. Use add_tags_to_item_version when only one version should be changed. |
| remove_tags_from_item | DecisionRules Management API tool for the authenticated space. Use when the user wants to remove one or more tags from every version of a rule or rule flow identified by ID or alias. Provide tags as a CSV query array, for example tags=production,pricing. Use remove_tags_from_item_version when only one version should be changed. |
| add_tags_to_item_version | DecisionRules Management API tool for the authenticated space. Use when the user wants to add tags to one exact version of a rule or rule flow identified by ID or alias plus version. The body must be an array of tag objects. Use add_tags_to_item when all versions should be changed. |
| remove_tags_from_item_version | DecisionRules Management API tool for the authenticated space. Use when the user wants to remove one or more tags from one exact version of a rule or rule flow identified by ID or alias plus version. Provide tags as a CSV query array, for example tags=production,pricing. Use remove_tags_from_item when all versions should be changed. |
| get_folder_tree_by_path | DecisionRules Management API tool for the authenticated space. Use when the user wants the root folder tree or folder-tree placement metadata for a folder or rule selected by path. Omit path for the root tree. A path must start with "/" and use folder and rule names, not IDs, for example /Client/Important. This does not return a complete rule definition; use get_rule_by_path when the rule content is needed. |
| create_folder_by_path | DecisionRules Management API tool for the authenticated space. Use when the user wants to create one or more folders under the root folder or under a folder selected by path. Omit path to create under root. If path is provided, it must start with "/" and use folder names, not folder IDs, for example /Client/Important. |
| overwrite_folder_tree_by_path | DecisionRules Management API tool for the authenticated space. Use when the user wants to replace the child folder structure under root or under a folder selected by path. This is an overwrite operation, so use create_folder_by_path for additive folder creation. If path is provided, it must start with "/" and use folder names, not folder IDs. |
| delete_folder_tree_by_path | DecisionRules Management API tool for the authenticated space. Use when the user explicitly wants to delete a folder selected by path, including descendant folders and rules. The path must start with "/" and use folder names, not folder IDs, for example /Client/Important. Use path=/ with deleteAll=true only when deleting all root items. |
| get_folder_tree | DecisionRules Management API tool for the authenticated space. Use when the user provides a folder node ID and wants folder-tree placement metadata under that node. Use get_folder_tree_by_path when the user provides a path such as /Client/Important. Rule entries contain placement metadata, not complete rule definitions; retrieve rule content with a get_rule tool. |
| create_folder | DecisionRules Management API tool for the authenticated space. Use when the user wants to create one or more folders under a folder selected by node ID. Use create_folder_by_path when the user provides a folder path. |
| overwrite_folder_tree | DecisionRules Management API tool for the authenticated space. Use when the user wants to replace the child folder structure under a folder selected by node ID. This is an overwrite operation; use create_folder for additive folder creation. |
| delete_folder_tree | DecisionRules Management API tool for the authenticated space. Use when the user explicitly wants to delete a folder selected by node ID, including descendant folders and rules. Use delete_folder_tree_by_path when the user provides a folder path. |
| export_root_folder | DecisionRules Management API tool for the authenticated space. Use when the user wants to export the entire root folder tree, including descendant folders and rules. Use export_folder when only a specific folder node should be exported. |
| export_folder | DecisionRules Management API tool for the authenticated space. Use when the user wants to export a folder selected by node ID, including descendant folders and rules. Use export_root_folder for the whole root tree. |
| import_folder_by_path | DecisionRules Management API tool for the authenticated space. Use when the user wants to import an exported folder tree into root or into a folder selected by path. Omit path to import into root. If path is provided, it must start with "/" and use folder names, not folder IDs, for example /Client/Important. |
| import_folder | DecisionRules Management API tool for the authenticated space. Use when the user wants to import an exported folder tree under a folder selected by node ID. Use import_folder_by_path when the user provides a folder path. |
| find_folder_node | DecisionRules Management API tool for the authenticated space. Search folder-tree placement metadata across both folders and rules. Use this when a folder may match or the node type is unknown; use find_rule_node for a rule-focused search. Returns matching placement records, not complete rule definitions, so use a get_rule tool when rule content is needed. |
| find_rule_node | DecisionRules Management API tool for the authenticated space. Use for a rule-focused folder-tree search by ruleAlias, ruleType, ruleStatus, tags, version, baseId, name, or node ID. Include at least one rule-specific field when results must exclude folders because name or node ID alone is not rule-exclusive. Returns placement metadata, not the complete rule definition. |
| move_folder_nodes | DecisionRules Management API tool for the authenticated space. Move folders, rules, or a mixed batch to an existing destination folder. Use this tool when any source node is a folder or source types are mixed; use move_rule_nodes for a rule-only batch. Include nodes plus exactly one destination selector, targetId or targetPath. A targetPath starts with "/" and uses folder names, not IDs. |
| move_rule_nodes | DecisionRules Management API tool for the authenticated space. Move a rule-only batch to an existing destination folder. Every source node must have type RULE and identify the rule by baseId or ruleAlias, with version when a specific version is intended. Include exactly one destination selector, targetId or targetPath. Use move_folder_nodes if any source is a folder. |
| rename_folder_by_path | DecisionRules Management API tool for the authenticated space. Use when the user wants to rename a folder selected by folder path. The path must start with "/" and use folder names, not folder IDs, for example /Client/Important. The body must include the new folder name. |
| rename_folder | DecisionRules Management API tool for the authenticated space. Use when the user wants to rename a folder selected by node ID. The body must include the new folder name. Use rename_folder_by_path when the user provides a folder path. |
| find_latest_rule_duplicates | DecisionRules Management API tool for the authenticated space. Use when the user wants to detect duplicate rows in the current/latest version of a decision table identified by rule ID or alias. Checks the highest version regardless of publication status. Use find_rule_version_duplicates when the user provides a version. |
| find_rule_version_duplicates | DecisionRules Management API tool for the authenticated space. Use when the user wants to detect duplicate rows in one exact decision-table version and provides rule ID or alias plus version. Use find_latest_rule_duplicates when no version is provided. |
| get_latest_rule_dependencies | DecisionRules Management API tool for the authenticated space. Use when the user wants dependency information for the current/latest version of a rule identified by rule ID or alias. Returns dependencies for the highest version regardless of publication status. Use get_rule_version_dependencies when the user provides a version. |
| get_rule_version_dependencies | DecisionRules Management API tool for the authenticated space. Use when the user wants dependency information for one exact rule version and provides rule ID or alias plus version. Use get_latest_rule_dependencies when no version is provided. |
| export_latest_rule_flow | DecisionRules Management API tool for the authenticated space. Use when the user wants to export the current/latest version of a rule flow identified by ID or alias, including referenced rules. Returns an array suitable for import_rule_flow. Use export_rule_flow_version when the user provides a version. |
| export_rule_flow_version | DecisionRules Management API tool for the authenticated space. Use when the user wants to export one exact rule-flow version identified by ID or alias plus version, including referenced rules. Returns an array suitable for import_rule_flow. |
| import_rule_flow | DecisionRules Management API tool for the authenticated space. Use when the user wants to import a rule-flow export array. The body must be the array returned by export_latest_rule_flow or export_rule_flow_version: first item is the rule flow, remaining items are referenced rules. Use new-version to create a new version of an existing rule flow, overwrite to replace an existing rule flow, version with overwrite/new-version when targeting a specific version, and folderId to place newly imported items into a folder node. |
| get_space_owner_statistics | DecisionRules Management API tool for the authenticated space. Use when the user asks about usage, limits, or pay-as-you-go consumption for the billing owner of the authenticated space. Returns API-call usage and limit, audit-log storage usage and bill, job-seconds usage and bill, and item usage and limits. This is an account-usage lookup, not a space inventory. |
| create_test | DecisionRules Management API tool for the authenticated space. Add and persist one rule test case in an existing DecisionRules test suite. testSuiteId selects the target suite, and the body supplies the test name, input, and expected output. This saves the test case but does not execute it. |
| update_test | DecisionRules Management API tool for the authenticated space. Update and persist an existing DecisionRules rule test case. testSuiteId selects the target suite, and the body must contain the test ID plus the complete updated test data. The saved last-run state is cleared; this operation does not execute the test. |
| move_tests | DecisionRules Management API tool for the authenticated space. Move selected DecisionRules test cases into a newly created destination suite. The body requires test ids, the target ruleAlias and ruleVersion, and name for the new suite. Use move_test_suites instead when retargeting whole existing suites. |
| delete_tests | DecisionRules Management API tool for the authenticated space. Permanently delete selected DecisionRules test cases while leaving their test suites in place. Use only on an explicit deletion request and provide ids as a comma-separated list of test IDs. Use delete_test_suites to remove whole suites. |
| import_generated_test_suites | DecisionRules Management API tool for the authenticated space. Review `generate_test_suite.result.value`, then pass it unchanged to this tool. Expected outputs are solved from each exact saved rule version before persistence; never calculate or add them manually. Every suite is bound to the authenticated space. |
| list_test_suites_for_rule | DecisionRules Management API tool for the authenticated space. List DecisionRules test suites attached to one exact rule alias and version. The alias parameter is ruleAlias, not a rule ID or display name. Use list_test_suites for a space-wide listing or filtering by suite ID. |
| list_test_suites | DecisionRules Management API tool for the authenticated space. List DecisionRules test suites in the authenticated space. Optionally pass filter as a JSON string containing ruleAlias, ruleVersion, or suite id, for example {"ruleAlias":"my-rule","ruleVersion":1}. Use list_test_suites_for_rule when an exact rule alias and version are already known. |
| create_test_suites | DecisionRules Management API tool for the authenticated space. Persistence-only operation for complete test suites whose inputs and expected outputs were explicitly supplied or approved by the user. Never invent expected outputs or use this tool for AI-assisted test generation. For AI-assisted coverage, call generate_test_suite and then pass its reviewed result to import_generated_test_suites so the solver resolves expected outputs. |
| update_test_suite | DecisionRules Management API tool for the authenticated space. Replace the saved data for one existing DecisionRules test suite. Pass the suite ID and the complete updated suite, including its tests and rule target. Test last-run state is cleared; this operation does not execute tests. |
| delete_test_suites | DecisionRules Management API tool for the authenticated space. Permanently delete one or more DecisionRules test suites and their contained test cases. Use only on an explicit deletion request and provide ids as a comma-separated list of suite IDs. Use delete_tests when removing individual cases only. |
| move_test_suites | DecisionRules Management API tool for the authenticated space. Retarget whole existing DecisionRules test suites, including their contained tests, to another ruleAlias and ruleVersion. The body requires suite ids and the new rule target. This does not create a new suite; use move_tests when selected cases should be collected into a new suite. |
| solve_rule | DecisionRules Solver API tool for the authenticated space. Execute an already saved DecisionRules rule by ID or alias with supplied input data and return its runtime output. This evaluates a rule; it does not create or modify one. Supply version only for an exact version, and use optional headers for execution strategy, debug mode, audit settings, correlation ID, or lookup method. |
| generate_decision_table | DecisionRules AIA authoring tool for the authenticated space. Use this as the default authoring tool when requested logic can be represented reliably and readably as declarative conditions and results. A formula, collection, or large request does not by itself require scripting; judge the actual capabilities the logic needs. This tool calls the DecisionRules AI engine and returns a structured result. It never saves the resource. Only when `result.type` is `SUCCESS`, review `result.value` and pass that resource object unchanged to create_rule. When `result.type` is `SEMANTIC_REVIEW_FAILED`, never create or import `result.value`; refine or retry the request. |