Agent Identity & Security
My agent is failing with 'unauthorized tool call' errors in Catalyst—how do I troubleshoot the identity or policy issue?
First, verify the agent’s workload identity is correctly provisioned by checking Catalyst’s identity registry. Then, review the tool authorization policy for that identity—ensure the tool name and action match exactly (MCP tool names are case-sensitive). Check if the policy has a deny rule that inadvertently blocks the call. Use Catalyst’s policy simulation tool to test the call without affecting production. Finally, inspect the audit log for the exact authorization decision.
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.