MCP tools
emfirge_compare_branches
Compare one or more isolated infrastructure branches and their modeled consequences across the documented lenses, including security outcomes.
Parameters
branch_ids: string[] · required
MCP ask / arguments
{ "branch_ids": ["branch_456", "branch_789"] }
Returns
The response is JSON shaped for the operation. The fields and semantics are described below.
JSON response
{
"base_analysis_id": "analysis_123",
"branches": [{ "branch_id": "branch_456", "name": "restrict-public-access", "score_after": 78, "score_delta": 6, "added_nodes": 0, "removed_nodes": 0, "newly_internet_reachable": 0, "no_longer_internet_reachable": 1, "added_findings": 0, "removed_findings": 1, "has_privilege_escalation": false }],
"ranking": ["branch_456"], "has_mixed_bases": false, "base_analysis_ids": ["analysis_123"]
}
Validation, behavior, and limits
Each branch summary reports score_after, score_delta, added_nodes, removed_nodes, newly_internet_reachable, no_longer_internet_reachable, added_findings, removed_findings, and has_privilege_escalation.
ranking orders branches safest-first using deterministic comparison; it is not a deployment recommendation or safety guarantee.
has_mixed_bases is true when branches come from different analyses. Compare different snapshots carefully and re-scan if the live account has changed.
Based on the Emfirge MCP and engine source.View source