docs/en/enterprise/features/agent-control-plane/rules.mdx
Rules let you apply policies — today: PII Redaction — across many automations at once, instead of configuring each deployment individually. Open the Rules tab in the Agent Control Plane to manage them.
<Frame>  </Frame>Each rule card shows the name, description, the scope the rule applies to (selected tools and tags), and a count of engaged automations — deployments that currently match the scope. The toggle on the right enables or disables the rule without deleting it.
manage RBAC permission on Agent Control Plane is required to create, edit, toggle, or delete rules. The read permission is enough to view them.| Type | What it does |
|---|---|
| PII Redaction | Applies PII redaction to executions of every matching automation, using the same entity catalog and custom recognizers documented in PII Redaction for Traces. |
More rule types will be added over time.
- **Tools** — only automations whose tool set **exactly matches** the selected tools will engage. Picks from Studio apps, MCPs, OSS tools, and Tool Repository registry tools.
- **Automations** — only automations whose tag set **exactly matches** the selected tags will engage.
Leaving a picker empty means "no filter on this dimension". Leaving both empty means the rule applies to **every** automation in the organization.
Click Engaged N automations on any rule card to see exactly which deployments the rule is currently matching, along with each one's last execution.
<Frame>  </Frame>This is the fastest way to sanity-check a rule's scope before enabling it — for example, to confirm that a rule scoped to the production tag isn't accidentally matching a staging deployment.
PII Redaction can be configured in two places:
When an enabled org-wide rule's scope matches a deployment, the rule's entity configuration overrides the deployment-owned PII settings for that deployment's executions — the rule becomes the single source of truth while it's attached. Disable or detach the rule (or change its scope so it no longer matches) and the deployment falls back to its own PII Protection settings.
Prefer org-wide rules when you want to enforce a consistent policy across many deployments; reserve per-deployment configuration for one-off exceptions.