Skip to main content
Glama

LexQ

by io.lexq.mcp
OverviewDiscussionsAdmin

Update Policy Group

lexq_groups_update
Destructive

Update a policy group. Only provided fields are updated; omitted fields remain unchanged. A deleted group cannot be updated (409 P-059).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew name
statusNoDISABLED stops production execution of this group: execution calls return 403 (P-009), and a composite call that includes the group is rejected in full. The deployed version and any A/B test are kept, and dry run, Impact Simulation, and Decision Replay keep working, so a fix can be verified before setting ACTIVE again. To go back to the previous version, use lexq_deploy_rollback. To take the version out of production, use lexq_deploy_undeploy.
groupIdYesPolicy group ID
descriptionNoNew description
activationModeNoConflict resolution mode
executionLimitNoHow many policy groups sharing this activationGroup may run. Counts groups, not rules.
activationGroupNoActivation group (Execution Group) cluster key. Policy groups sharing this key compete, and group priority picks the winners.
activationStrategyNoRanking used to pick the winning groups

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / status / description
      Previous value: -"Status (DISABLED = emergency stop)"New value: +"DISABLED stops production execution of this group: execution calls return 403 (P-009), and a composite call that includes the group is rejected in full. The deployed version and any A/B test are kept, and dry run, Impact Simulation, and Decision Replay keep working, so a fix can be verified before setting ACTIVE again. To go back to the previous version, use lexq_deploy_rollback. To take the version out of production, use lexq_deploy_undeploy."
  2. Changed8 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / activationGroup / description
      Previous value: -"Activation group (Execution Group) cluster key"New value: +"Activation group (Execution Group) cluster key. Policy groups sharing this key compete, and group priority picks the winners."
    • changedInput schema / properties / activationStrategy / description
      Previous value: -"Strategy"New value: +"Ranking used to pick the winning groups"
    • changedInput schema / properties / activationStrategy / enum
      Previous value: -[
-  "FIRST_MATCH",
-  "HIGHEST_PRIORITY",
-  "MAX_BENEFIT"
-]New value: +[
+  "HIGHEST_PRIORITY"
+]
    • changedInput schema / properties / executionLimit / description
      Previous value: -"Max rule executions"New value: +"How many policy groups sharing this activationGroup may run. Counts groups, not rules."
    • addedInput schema / properties / executionLimit / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / groupId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Changed2 schema fields changed
    • addedInput schema / properties / activationGroup
      Added value: +{
+  "description": "Activation group (Execution Group) cluster key",
+  "type": "string"
+}
    • removedInput schema / properties / priority
      Removed value: -{
-  "description": "New priority",
-  "minimum": 0,
-  "type": "integer"
-}
  4. Changed6 schema fields changed
    • addedInput schema / properties / activationMode
      Added value: +{
+  "description": "Conflict resolution mode",
+  "enum": [
+    "NONE",
+    "EXCLUSIVE",
+    "MAX_N"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / activationStrategy
      Added value: +{
+  "description": "Strategy",
+  "enum": [
+    "FIRST_MATCH",
+    "HIGHEST_PRIORITY",
+    "MAX_BENEFIT"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / conflictResolutionMode
      Removed value: -{
-  "description": "Conflict resolution mode",
-  "enum": [
-    "NONE",
-    "EXCLUSIVE",
-    "MAX_N"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / conflictResolutionStrategy
      Removed value: -{
-  "description": "Strategy",
-  "enum": [
-    "FIRST_MATCH",
-    "HIGHEST_PRIORITY",
-    "MAX_BENEFIT"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / executionLimit
      Added value: +{
+  "description": "Max rule executions",
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / properties / maxSelections
      Removed value: -{
-  "description": "Max selections",
-  "minimum": 1,
-  "type": "integer"
-}
  5. First observed

TDQS

Score is being calculated.

All LexQ toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources