Skip to main content
Controls let you attach policy artifacts — such as PII filters and content guardrails — to agents, tools, and models. When a control is active, the platform applies the policy at the configured execution hooks, for example before an agent runs or after a tool responds.

Prerequisites

  • You must be authenticated. See Initiating your environment.
  • Controls require the controls feature to be enabled in your watsonx Orchestrate instance. Contact your administrator if the orchestrate controls commands are unavailable.

Viewing available policy types

Before creating a control, list the policy artifact types available in your instance:
BASH
To see full details for a specific type:
BASH
Use the artifact name shown here as the --artifact value when creating a control.

Creating a control

Bind a policy artifact to one or more agents, tools, or models:
BASH

Example: Content guardrails on an agent

BASH

Importing controls from a file

Define one or more controls in a YAML file and import them all at once. This approach is useful for scripting and CI/CD workflows.
BASH
Example YAML file:
YAML

Listing controls

List all controls in your active environment:
BASH
Filter by a specific asset:
BASH
Use --verbose to show full JSON details:
BASH

Getting control details

BASH

Updating a control

Update specific fields of an existing control. Only the fields you provide are changed:
BASH
When you update --agent, --tool, or --model values, the provided list replaces the existing bindings for that asset type entirely. To keep existing bindings, include them alongside the new ones.

Exporting a control

Export a control to a YAML file to version it or re-import it in another environment:
BASH

Removing a control

BASH
This removes the control and all of its associated bindings.