Enforce cloud budget limits for Slack bot agents

Slack bots that scale cloud spend from chat introduce cost and compromise risk. Call evaluate inside the handler before the scale API so channel budget policy must allow the cost first.

Wire evaluate into the handler path

1. Slack command: A developer runs /aws scale database db.r5.12xlarge.
2. Handler trigger: Slack invokes the handler.
3. Build the intent: Parse the request, map the instance tier to an estimated hourly cost, and submit evaluate to Limetry.
4. Enforce the decision: If cost exceeds the channel budget (for example max $100/hr), Limetry denies and Slack returns an authorization error.

Even if Slack is compromised, the scale API still waits on an allow decision and a privacy-safe audit record.

Deploy with the Slack bot example. Point evaluate at your self-run Limetry server — see [self-run setup](/docs/server/self-run setup).