Agent Identity & Security
What is the architecture for least-privilege agent identity in Catalyst?
Catalyst binds each agent runner to a unique workload identity, separate from human or service identities. Tool authorization policies map identities to specific MCP tools or API endpoints, with granular permissions like read-only or write-scoped. The architecture uses Dapr’s service invocation with mTLS, so every call carries the agent’s identity for policy enforcement.
Was this article helpful?
Your feedback helps improve Diagrid's FAQ experience.
Keep reading
More Diagrid FAQ articles
- Agent Identity & Security
What is a workload identity for an AI agent and why can't I just use a shared API key?
Explains workload identity for AI agents and the security limits of shared API keys in production.
- Agent Identity & Security
How does Catalyst assign a workload identity to an agent runner like LangGraph or CrewAI?
Describes how Catalyst injects workload identities into framework-agnostic agent runners.
- Agent Identity & Security
What security problems do shared API keys cause when multiple agents run in production?
Lists security problems from shared API keys in multi-agent production environments.