2.0.0

run_kql: the first real tool surface

The CIDR launch tools give way to the server's purpose: agents (Security Copilot among them) reaching into the Azure estate over MCP. run_kql executes a read-only KQL query against an Azure Log Analytics workspace with two gates in front of every query: the deployment's workspace allow-list (a Terraform-managed app setting; the tool refuses anything off it before RBAC even gets a say) and the identity's own Log Analytics Reader role, granted only where the stack points it. Results are capped (100 rows, long cells truncated) so one query cannot flood a model's context. The major version reflects the removed tools; the mechanism, stack shape, and justfile flow are unchanged.

Security Copilot

Research finding baked into the repo: Security Copilot consumes MCP servers as custom plugins (Preview) but its manifest can only express OAuth or Entra delegated auth, so the default key-auth deployment cannot register there. manifests/security-copilot.yaml ships ready to fill in, documenting the target shape; the built-in Entra authorization milestone is the path to it. Every header-capable MCP client works today with the system key.

Proven live before release: a full MCP session against the deployed server listed the tool, had an unlisted workspace refused by the allow-list, and got a live KQL answer from the test workspace through the managed identity, then the stack was destroyed.

Full diff: 1.0.0...2.0.0