Visual Security Boundaries for Enterprise AI
Why MCP Tool Access Does Not Replace Runtime Identity
MCP can narrow which tools an agent may call, but it does not replace runtime identity, delegated user access, or downstream system permissions.
Ideas
I write about how enterprise AI gets built.
Thesis pieces, frameworks, build notes, and security briefs on the infrastructure, runtimes, and control layers underneath enterprise AI.
7 ideas Search by title, topic, or series.
Latest publication
Archive
Framework Security Boundaries for Enterprise AI
Agent Identity Patterns: Which One to Use, and When
The real choice is not whether an agent has credentials. It is which identity pattern fits the ownership boundary around the action.
Thesis The AI-Ready Enterprise Stack
The AI-Ready Enterprise Stack
Most enterprise AI conversations start at the model layer. They should start several layers lower.
Build Note Inside the Agent Runtime
What Every Agent Runtime Should Share
Triggers, validation, recovery, and auditability belong in the scaffold, not re-invented agent by agent.
Security Brief Security Boundaries for Enterprise AI
Why MCP Is a Trust-Boundary Problem
The problem is not connector count. It is identity, scope, trust boundaries, and what the runtime is allowed to do.
Framework
Decision Automation Needs Three Layers, Not One
Rules, ML signals, and LLM reasoning each have different jobs. Treating them as one layer creates brittle systems.
Contrarian
Stop Calling Every Workflow an Agent
Autonomy, recovery, and access boundaries matter. Without them, it is automation wearing new language.
No ideas match the current filters
Try a different topic, format, or search term.