privy policies rules update

Replace a rule definition in an unowned policy; all four fields are required.

Usage

privy policies rules update [options] <policy-id> <rule-id>

Arguments

Argument	Description
policy-id	—
rule-id	—

Options

Option	Description
--dry-run	Validate and print the API request without network access or credentials.
--yes	Confirm this mutation or export.
--body <json>	JSON body, or - to read stdin.
--file <path>	JSON body file, or - to read stdin.
--name <string>	Policy or rule display name (1–50 characters).
--method <string>	Policy method, e.g. eth_sendTransaction, or * for all methods. Privy validates compatibility with the policy chain.
--action <string>	Action when the conditions match: ALLOW or DENY.
--conditions <json>	Complete condition array as JSON (replaces existing conditions). Uses the Privy policy language; nested condition semantics are validated by Privy, not fully modeled locally.
--diff	Read live state and show changes WITHOUT writing (requires login).
--allow-production	Explicitly allow this production mutation; also requires --yes.

Global options such as --app, --account and --profile also apply. See the command reference overview.

Examples

privy policies rules update <policy-id> <rule-id> --file rule.json --diff
privy policies rules update <policy-id> <rule-id> --file rule.json --yes

Behavior

• Changes data: yes. Preview with --dry-run, then run with --yes and any required confirmations.
• Scope: app
• Before it runs: Read app environment; existing policies must have owner_id: null. Policy deletion also requires exact name and deletable: true.
• Production apps: Requires --allow-production in addition to --yes.
• Verification: Fresh policy read and field comparison; deletion requires verified absence.
• Retries: None.

Related guides

• Policies and approvals
• Failure recovery

Inspect the full contract locally with privy schema policies rules update.