Example starting policies

Example starting policies

Examples to start from and edit, not recommendations for your environment — you decide what your policy should say. Each example is Aarmatix-signed and verified on this device before it can be activated, the same code path as any pasted bundle in Settings → Signed policy.

  • PII Redaction

    Verifying…

    Redact email, phone, SSN, card numbers, and common API key prefixes in tool inputs and outputs.

    • Redacts 5 pattern classes before tool call and after tool return
    • Applies to every tool — no per-tool opt-in required

  • Daily Budget Cap

    Verifying…

    Cap every agent at $5 spend per UTC day and 20 steps per run.

    • Autonomous scope $5/day per agent (UTC)
    • Hard ceiling of 20 steps per single run tree

  • No External Network

    Verifying…

    Only allow tools that talk to localhost. Deny generic http, fetch, and shell tools.

    • allowedServers pinned to 127.0.0.1 / localhost
    • Denies http_*, fetch_*, shell_* by glob

  • Approval Required For Writes

    Verifying…

    Block every write-shaped tool by default. Approve individual calls at runtime.

    • Blocks write_*, delete_*, update_*, create_*, put_*, post_*, patch_*, send_*, pay_*, transfer_*
    • Reads remain unrestricted

  • Tenant Isolation

    Verifying…

    Read-only scopes for github, slack, notion, gdrive. Deny admin and workspace-delete tools.

    • Pinned read-only scopes per connector
    • Denies *_admin_*, *_org_*, *_workspace_delete_*

  • Kill Switch Default-On

    Verifying…

    Boot every session halted. Operator must explicitly release. Denies shell and eval tools.

    • killSwitchDefault = true
    • Denies shell_*, *_exec_*, *_eval_*