Server Wallet: Policy
resource: policy — spend/governance policies (POL01–POL05)
create (POL01) wallet secret required, fail-closed/unconfirmed
| Field | Required | Description |
|---|---|---|
policyJson | ✓ Yes | Raw JSON policy document, passed through as-is. |
Output: single policy record.
get (POL02)
| Field | Required | Description |
|---|---|---|
policyId | ✓ Yes | The policy to look up. |
Output: single policy record.
list (POL03)
No operation-specific config keys. Output items[], one entry per policy.
update (POL04) wallet secret required, fail-closed/unconfirmed
| Field | Required | Description |
|---|---|---|
policyId | ✓ Yes | The policy to update. |
policyJson | ✓ Yes | Replacement raw JSON policy document. |
Output: single policy record.
delete (POL05) wallet secret required, fail-closed/unconfirmed
| Field | Required | Description |
|---|---|---|
policyId | ✓ Yes | The policy to delete. |
Output: confirmation only.
What are policies for? CDP policies let you enforce spend rules (allow-lists, per-transaction limits, etc.) on a wallet or smart account at the platform level, so the rule is enforced even if this node's own config is misused.
Read operations (
get, list) do not require the Wallet Secret — only the three write operations above do, under the same fail-closed policy as the faucet operations. See Configuration.