The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Feb 18, 2026 8:54am

Greptile Summary

This PR adds a comprehensive audit logging system across the platform, instrumenting 53 API routes with fire-and-forget audit trail recording. It also includes a significant rework of the MCP domain validation logic to properly handle environment variable references in URLs.

Key changes:

• New audit_log table with nullable FKs (ON DELETE SET NULL), four indexes for workspace/actor/resource/action queries, and a Drizzle schema definition with matching migration
• recordAudit() utility in lib/audit/log.ts — fire-and-forget with IP extraction from headers and silent error swallowing
• Type-safe AuditAction and AuditResourceType enums (though all 53 call sites already use the enums correctly, not string literals)
• auditMock added to @sim/testing package, with 14 test files updated to mock the new module
• MCP domain check refactored: removed auto-allow for platform hostname, added hasEnvVarInHostname() for RFC 3986-aware authority parsing, and added post-resolution validation in McpService.resolveConfigEnvVars() and the test-connection route
• Client-side MCP settings component updated with matching hasEnvVarInHostname() logic and improved domain-blocked UI behavior
• checkChatAccess and checkFormAccess utilities extended to return workspaceId, eliminating redundant DB queries

Minor concerns:

• The auditMock manually duplicates all enum values from the source — it will silently drift if new actions are added
• description || null change in chat/form creation routes is schema-correct but is a behavioral change from the previous description || ''

Confidence Score: 4/5

• This PR is safe to merge — audit logging is fire-and-forget with no impact on request paths, and MCP domain validation improvements close a real security gap.
• Score of 4 reflects a well-structured, large-scale change with thorough test coverage. The audit system's fire-and-forget design means failures won't break any user-facing functionality. The MCP domain check rework is well-tested with 63 test cases. Minor deductions for: manually duplicated mock enum values that may drift, and the behavioral change from '' to null for description defaults.
• packages/testing/src/mocks/audit.mock.ts (manual enum duplication risk), apps/sim/app/api/chat/route.ts and apps/sim/app/api/form/route.ts (description default change from '' to null)

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[API Route Handler] -->|Success path| B[recordAudit]
    B --> C{Build audit entry}
    C --> D[Extract IP from headers]
    C --> E[Set workspaceId / actorId]
    C --> F[Set action / resourceType]
    D --> G[db.insert audit_log]
    E --> G
    F --> G
    G -->|.then| H[Log debug]
    G -->|.catch| I[Log error silently]
    A -->|Return response| J[HTTP Response]

    subgraph MCP Domain Validation
        K[URL input] --> L{Has env var in hostname?}
        L -->|Yes| M[Bypass domain check]
        L -->|No| N{Domain in allowlist?}
        N -->|Yes| O[Allow]
        N -->|No| P[Reject]
        M --> Q[Validate after env var resolution]
        Q --> N
    end

_{Last reviewed commit: 6d406c1}

@cursor review

@greptile

@greptile

@cursor review

@cursor review

@greptile

@greptile

@cursor review