Skip to main content

Security and audit

Security and permissions​

The MCP server does not bypass existing access controls. Every tool call uses the authenticated user's or API key's permissions, and the selected endpoint limits which organization or instance the agent can reach.

  • Enabling the platform endpoint does not automatically expose every instance. Instance access is a separate opt-in control.
  • The guardrail level limits MCP tool calls on both endpoint types and never grants additional access. Delegated Akuity agent actions follow separate Akuity Agents tool policies.
  • Approving an Akuity Agents tool action through MCP requires update permission on the target instance and the Full guardrail level.
  • Write operations that change managed state through MCP are recorded in the audit log under the authorizing user or API key and tagged via MCP. See Audit.
  • Review tool calls before approving them.
  • Ordinary conversations started through the platform endpoint require a target instance and are shared with its authorized users. Ordinary conversations started through a direct endpoint are initially private to their creator. Incident investigations and promotion analyses are shared operational records on either endpoint.
  • Treat application manifests, diffs, events, and workload logs as potentially sensitive data.
  • Use least-privilege accounts and API keys, and rotate credentials according to your organization's policy.

Audit​

Write operations that change managed state through MCP appear in the organization audit log under the user or API key that authorized them, tagged via MCP. Read-only operations, application refreshes, and Akuity Agents conversations do not create audit entries.

  1. In the Akuity Portal, open Audit Logs. The Owner role or a custom role with audit-log read permission is required.
  2. Open the Actor filter and check Via MCP only.

Audit log filtered to MCP

The same filter is available in the Audit Logs tab inside the Argo CD and Kargo UI. The CSV export includes an ActorOrigin column. Retention and archives follow the standard Audit Logs behavior.