Agent Identity & Security
How do I troubleshoot an agent failing to call an internal API due to identity policy in Catalyst?
Check Catalyst’s audit logs for denied authorization events, which show the agent identity, target tool, and policy rule that blocked the call. Verify the agent’s workload identity matches the policy’s allowed identities. Ensure the MCP tool is registered with the correct endpoint and method. Use Catalyst’s policy dry-run mode to test changes without affecting production.
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.