Atmos Pro Logo

Atmos Pro

ProductPricingDocsBlogChangelog
Create Workspace
← Back to Changelog
Enhancement

Your agent can now see which features are switched on

Erik Osterman

Erik Osterman

CEO & Founder of Cloud Posse

|June 1, 2026

Older

AI Credits for Atmos AI

Newer

Status Feed Reports Incidents, Not 'All Clear'

Erik Osterman

Erik Osterman

CEO & Founder of Cloud Posse

Erik is the founder of Cloud Posse and creator of Atmos. With over a decade of experience helping teams adopt Terraform at scale, he is passionate about open-source infrastructure tooling and developer experience.

Book a Meeting
Atmos Pro Logo

Atmos Pro

The fastest way to deploy your apps on AWS with Terraform and GitHub Actions.

GitHubTwitterLinkedInYouTubeSlack

For Developers

  • Quick Start
  • Example Workflows
  • Atmos Documentation

Community

  • Register for Office Hours
  • Join the Slack Community
  • Try our Newsletter

Company

  • About Cloud Posse
  • Security
  • Pricing
  • Blog
  • Media Kit

Legal

  • SaaS Agreement
  • Terms of Use
  • Privacy Policy
  • Disclaimer
  • Cookie Policy

© 2026 Cloud Posse, LLC. All rights reserved.

Checking status...

"Why can't I use this feature?" — answered by your agent

A feature like the Cross-Repo Token Broker needs two separate things turned on: your plan has to include it, and an admin has to flip its switch on the Settings → Security tab. Until now an agent connected over MCP could read your plan entitlements (list_entitlements) but had no way to see the workspace toggle. So when token minting refused, the agent could tell you the plan gate — but never that the switch was simply off.
The new get_workspace_settings tool closes that gap. It returns the per-workspace admin toggles — stsEnabled (Cross-Repo Token Broker) and githubChatopsEnabled — alongside the existing entitlement view. Ask your agent "why can't I mint cross-repo tokens?" and it now checks both gates and tells you exactly which one is closed: plan not entitled, or entitled but toggled off.
The tool is read-only and scoped to the workspace your MCP token is bound to, like the rest of the workspace introspection tools. Enabling a feature is still a deliberate action you take in the dashboard — the agent can see the switch, not flip it.