Security audit
Security checks for vulnerabilities and agentic risk
The skill’s email, calendar, optional file access, and automation features are disclosed and include clear user approval controls.
Connect only accounts and knowledge files you want the agent to read. Read content may enter your model provider’s context. Review action previews, enable automatic replies only with suitable limits, and verify approval behavior in the server version you install.
Identity configuration could support email setup, but adding a local pricing spreadsheet to an identity is not explained by the declared email and calendar workflows. The chunk does not establish whether the file is transmitted or whether approval controls are bypassed; the mismatch is the undisclosed local-file operation.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
the server's `env` block (see Setup step 3).
- Approvals the user grants "don't do anything" → same cause: server and
console must share `GIGAMAIL_ROOT`.
- Approving from the CLI fails with "no consent backend" → that machine
has no Windows Hello / Touch ID. On Linux the user sets a PIN with
`gigamail approvals pin`; elsewhere they approve from the desktop
console. `gigamail approvals check` shows which verification the machine
No suspicious patterns detected.