add_credential
Store a credential using name, alias, URL, and tag lookup keys so agents can retrieve it later without exposing secrets in chat.
Instructions
Store a new credential. Keys the agent can later look it up by: name, aliases, urls
(full URLs, bare hosts, or wildcards like *.corp.com), and tags.
secret_source (how the main secret is obtained — prefer ones that keep it out of the chat):
prompt (default) user types it into a secure macOS dialog
clipboard read from clipboard, then clear it (user copies it first)
file read from `secret_file` (great for SSH keys / service-account JSON)
generate create a strong random password/passphrase
value use `secret` as given (only if the user already pasted it in chat)
none no main secret (e.g. only extra_secrets / notes)
`secret_field` overrides the field name (default depends on type: password/token/key/...).
`extra_secrets` e.g. {"totp_secret": "JBSW..."} or {"api_secret": "..."}.
`fields` = non-secret extras, e.g. {"host": "db.internal", "port": "5432", "region": "ap-south-1"}.
policy: open | confirm | sealed | strict (default from config).Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| tags | No | ||
| type | No | password | |
| urls | No | ||
| notes | No | ||
| fields | No | ||
| policy | No | ||
| secret | No | ||
| aliases | No | ||
| username | No | ||
| expires_at | No | ||
| rotate_days | No | ||
| secret_file | No | ||
| secret_field | No | ||
| extra_secrets | No | ||
| generate_kind | No | password | |
| secret_source | No | prompt | |
| generate_length | No |