Use agents with Varroa
An agent in Varroa acts as a person, with that person’s permissions, and never as an administrator token.
Choose a way to connect
Section titled “Choose a way to connect”| Way | Who acts | Writes | Page |
|---|---|---|---|
| Your own MCP client | You, through your API key | The client calls write tools directly. Your grants are the gate. | Connect a client |
| The assistant in the dashboard | You, while you are signed in | Every write waits for your approval. | Assistant |
What every agent shares
Section titled “What every agent shares”Both ways use one tool surface, one grant check, and one audit trail. MCP does not provide a shell or unrestricted Kubernetes access. See Identity and auditing and Tool reference.
- Connect an MCP client, or turn on the assistant.
- Confirm the identity with
get_me. - Confirm effective access with
get_my_permissions. Then review the roles for each identity in Identity and auditing. - Read Writing through MCP before you change resources.
Apply guardrails
Section titled “Apply guardrails”- Give each client its own API key.
- Grant only the namespaces, controllers, and actions it needs.
- Review tool annotations before approving writes.
- Fetch one resource when a summarized list lacks required detail.
- Treat field-conflict overrides as a deliberate ownership transfer.
- Review activity events for mutations.
- Treat
call_jenkins_toolas open-ended because the target plugin defines its effects.
Credentials and sensitive status fields are removed from tool results. See Tool behavior for result shapes and redaction.