MCP tools
emfirge_get_branch
Read a branch’s metadata and its ordered, normalized change log without returning the base infrastructure snapshot.
Parameters
branch_id: string · required
MCP ask / arguments
{ "branch_id": "branch_456" }
Returns
The response is JSON shaped for the operation. The fields and semantics are described below.
JSON response
{
"branch_id": "branch_456", "name": "restrict-public-access", "status": "open",
"base_analysis_id": "analysis_123", "num_changes": 1,
"changes": [{ "op": "modify", "resource_type": "security_group", "resource_id": "NAME_132", "fields": { "rules": [] } }],
"branch_revision": "3f9a…c21e"
}
Validation, behavior, and limits
Returns branch_id, name, status, base_analysis_id, num_changes, the ordered changes, and branch_revision.
branch_revision is a SHA-256 of the branch history. Pass it to apply, rollback, rollback-to-count, or discard to reject a stale view with HTTP 409, even when another agent replaced history without changing its length.
The base snapshot is intentionally omitted to keep responses small.
Based on the Emfirge MCP and engine source.View source