AI Agent Orchestration Platform · View 09 of 32 · 2 · Structure
Decisions
- Tools are out-of-process and least-privileged; the runtime holds no long-lived tool credential
- A tool the registry does not list cannot be invoked, whatever the model emits
- Sensitive tools are marked in the registry and their approval requirement is a property of the tool, not of the prompt
Contract requirements
- Strong input and output schemas, a version, a health check and a declared timeout for every tool
- Idempotency key on every mutating call, derived from execution id, step id and the argument hash
- Per-agent and per-tenant rate limits, enforced at the gateway rather than in the tool
Risks
- MCP servers are a young ecosystem; partner servers are treated as untrusted and run behind the gateway with no network path to internal data
- Idempotency depends on the downstream system honouring the key; where it does not, a compensation step is mandatory
- Browser and computer-use tools carry the widest blast radius and are default-denied at organisation scope