Cursor AI Agent Reportedly Deleted a Production Database in 9 SecondsFEATUREDNEW
Cursor agent reportedly wiped a Railway production database and backups in one API call. Prompts aren't permissions — agents need pre-execution gates.
Engineering insights, product updates, and best practices for AI agent runtime authority, exposure, and cost control.
Tools you can run on your own numbers: Cost Calculator (Claude vs GPT) → · Blast Radius Risk Calculator → — every configuration produces a shareable URL. Many of the posts below link to a calculator pre-loaded with the post's specific scenario.
New to Cycles? Read these posts in order to understand runtime authority from the ground up.
Ready to try Cycles? Jump to the End-to-End Tutorial.
Cursor agent reportedly wiped a Railway production database and backups in one API call. Prompts aren't permissions — agents need pre-execution gates.
Agents span providers, tools, tenants, and workers. Tool-local controls govern only one slice — here is why agent governance has to be cross-cutting.
AI agents moved to production faster than governance kept up. This is the state of enforcement, regulation, and incidents in 2026 — and what comes next.
A practical guide to assessing AI agent risk at the tool level. Classify actions by blast radius, assign risk scores, and convert assessments into enforceable runtime budgets.
Documented AI agent incidents and recurring failure patterns — runaway costs, action misfires, security exploits, and multi-agent cascades. Each scored by cost, blast radius, and which runtime controls would have prevented it.
Agent skills turn reusable workflows into executable supply chain risk. Govern them with inventory, provenance, sandboxing, runtime limits, and audit.
MCP gateways help secure tool connectivity, but production agents still need runtime authority for budget, risk, scope, and per-action decisions at runtime.
Why production AI agents need dedicated identities, scoped credentials, owner mapping, audit trails, and runtime authority instead of borrowed user sessions.
A production webhook delivery contract for AI agent events: signed bodies, retries, dedupe keys, stale cutoffs, auto-disable, replay, and traceability.
Why AI agent platforms need previewed, idempotent bulk actions to contain tenant, webhook, and budget incidents without blind production scripts at 2 AM.
How to scope AI agent API keys by tenant, environment, and permission so one leaked credential cannot become cross-tenant budget authority in production.
Cursor agent reportedly wiped a Railway production database and backups in one API call. Prompts aren't permissions — agents need pre-execution gates.
Runtime authority's hidden byproduct: ledger-ready audit, cost, and attribution records for AI agents — useful for compliance, FinOps, and platform chargeback.
Multi-agent failures aren't a prompt problem. They're structural. A look at the UC Berkeley MAST taxonomy and the prevention patterns that actually work.
How to run the Cycles events service in production: the 7980/9980 port split, Prometheus scraping, Kubernetes probes, and alert rules that actually page the right people.