When to Use Re-analysis
Use re-analysis when:- New servers added: You’ve added MCP servers to Runlayer that may match existing shadow servers discovered on devices
- Catalog updates: The MCP catalog has been updated with new server definitions
- Policy changes: You want to refresh classifications after updating your organization’s MCP policies
How to Re-analyze
Configure Options
Click Re-analyze Servers and configure:
- Shadow servers only (default): Only re-analyze servers currently classified as shadow. This is recommended for most use cases.
- Uncheck to re-analyze all servers, including those already classified as managed.
Run Re-analysis
Click Start Re-analysis to begin. Results will display:
- Servers Analyzed: Total servers evaluated
- Servers Reclassified: Number of servers whose classification changed
- Newly Managed: Servers that changed from shadow to managed
- Newly Shadow: Servers that changed from managed to shadow (rare, typically indicates a deleted server)
Re-analysis Results
After re-analysis completes, the card displays a summary of changes:| Metric | Description |
|---|---|
| Servers Analyzed | Total number of servers evaluated during re-analysis |
| Servers Reclassified | Servers whose classification changed (shadow ↔ managed) |
| Newly Managed | Shadow servers that now match a Runlayer-managed server |
| Newly Shadow | Managed servers whose linked resource no longer exists |
Re-analysis always creates an audit log entry when triggered, recording who initiated it, the filters used, and a summary of results. Additional audit log entries are created for each server that is reclassified, providing a complete trail for compliance and security review.