AI-suggested exclusion rules and true MCP server names in cost telemetry

Tuning risk policies gets easier: describe the traffic you want to exclude and let AI draft the exclusion rule for you, with structured match fields validated before they reach the form. Cost telemetry also gets more truthful — sessions from user-configured MCP servers in Claude now report their real server and tool names instead of a generic "custom" label, so usage breakdowns reflect what your agents actually called.

Features

• Suggest exclusion rules with AI #4129 - The exclusion create/edit form gains a "Suggest with AI" option that returns structured match fields (match type, match value, and rule filters) ready to apply, with regex suggestions validated server-side before they reach the form. (Author: @claude)
• Real MCP server names in cost telemetry #4122 - Claude redacts the names of user-configured MCP servers in its cost telemetry. The platform now recovers the true server and tool attribution from session transcripts, so cost and usage summaries show which MCP servers were actually used instead of a generic "custom" label. (Author: @subomi)
• Shadow MCP inventory API #3852 - A new project-scoped API lists the Shadow MCP servers observed in your organization, with generated client SDK support, laying the groundwork for exploring unsanctioned MCP usage programmatically. (Author: @alx-xo)

Bug fixes

• Remote session and tunnel fixes #3968 - Organization-level remote session clients can now be deleted, tunnel gateway URLs are derived from the active environment, and remote identity providers can be detached without deleting shared clients. (Author: @ThomasRooney)