Tools reference

Twenty-one tools, each one a thin wrapper over a CLI command. You rarely name them — the agent picks — but knowing what exists tells you what you can ask for.

Environment files

| Tool | What it does | | --- | --- | | oneguard_env_sync | The main one. Pulls the linked secret into the directory's .env, linking it the first time | | oneguard_env_push | Uploads the local .env back into the linked secret, replacing it | | oneguard_env_status | Whether a directory is linked, to what, and which variable names its .env holds | | oneguard_env_unlink | Removes the .oneguard link file; leaves .env alone |

Every one of these takes an absolute project_dir. The server runs outside your shell, so a relative path would be meaningless — and a path that resolves outside the given directory is refused.

Generating values

| Tool | What it does | | --- | --- | | oneguard_generate | Generates values locally and returns them. Stores nothing | | oneguard_secrets_generate | Generates a value into a secret, merging, without revealing it |

Vaults and secrets

| Tool | What it does | | --- | --- | | oneguard_vault_list / _add / _rename | Vaults | | oneguard_secrets_list | Secrets in a vault — names and archive state, never values | | oneguard_secrets_add | Creates a secret from a .env file or a single pair | | oneguard_secrets_edit | Replaces a secret's whole payload | | oneguard_secrets_archive / _delete | Archive or permanently delete |

Team and organization

| Tool | What it does | | --- | --- | | oneguard_teams_list / _invite / _set_role / _remove | Members, invitations and roles | | oneguard_logs_list | The organization audit log |

Session

| Tool | What it does | | --- | --- | | oneguard_status | CLI found, session valid, backend reachable, and whether the key can write | | oneguard_init | Initializes the session with a key. Rarely needed — the server does it itself from ONEGUARD_API_KEY |

Deliberate gaps

Four CLI capabilities have no tool, on purpose:

• auth logout — there is no reason for an agent to be able to sign itself out. Clear ~/.oneguard-mcp instead.
• secrets set-path — it writes a hidden global default for where .env files land. Every tool here takes an explicit path; a hidden default would let an agent write somewhere nobody expected.
• secrets generate --show — the point of that tool is that the value never appears. An opt-out would make the guarantee negotiable.
• A one-off env pull — oneguard_env_sync always writes the link file. Pulling without linking is the one gap that is a limitation rather than a choice.