-
Notifications
You must be signed in to change notification settings - Fork 1
Operations and Audit
Use the operational pages to check key health, inspect recent activity, investigate failures, and update runtime safeguards.
The dashboard summarizes total, active, and revoked keys together with recent audit outcomes. Security signals and quick actions provide a starting point for routine checks.
Audit events cover MCP execution and administration changes. Filters can narrow results by action, keyword, date, outcome, actor, database, MCP key, or tool.
An event may include request and session identity, duration, returned or affected rows, approval status, error category, and a normalized query or DML definition.
Use audit data to answer three questions:
- What operation ran?
- Which identity and database were involved?
- Was it allowed, declined, rejected by policy, or failed during execution?
Runtime query limits, SQL timeout, DML safeguards, default key quotas, and SQL concurrency are edited under Runtime > Security Policy. The Admin database stores the authoritative values.
See Security Governance for defaults and enforcement order. For multi-replica propagation, see Distributed Deployment.
hs-sql-agent — GitHub | Apache License 2.0

