Since BAM does not provide native API throttling, what best practices or supported configurations exist to prevent LiveAssist MCP queries from overloading BAM resources in large dataset environments?
BlueCat BAM does not currently provide built‑in API throttling or query thresholds, meaning LiveAssist MCP queries can potentially overload BAM if not managed externally.
What is the maximum dataset size LiveAssist MCP has been benchmarked against, and how does performance scale with larger datasets?
Are there architectural guidelines for deploying LiveAssist MCP in environments with high‑volume DNS/DHCP/IPAM data, and how should BAM be tuned to support this?