MCP tools

emfirge_apply_change

Apply an add, modify, or delete change to a resource in an isolated branch; this changes the branch model, not AWS.

Parameters

branch_id: string · required; op: add | modify | delete · required; resource_type: string · required; resource_id: string · required; fields: record<string, unknown> · optional

MCP ask / arguments
{ "branch_id": "branch_456", "op": "modify", "resource_type": "security_group", "resource_id": "NAME_132", "fields": { "ingress": [] } }

Returns

The response is JSON shaped for the operation. The fields and semantics are described below.

JSON response
{ "branch_id": "branch_456", "num_changes": 1 }

Validation, behavior, and limits

fields contains fields to add or modify; omit it for delete or when no fields are needed. The operation validates the modeled target and returns the number of ordered changes currently recorded.

Resource IDs from scan responses may be tokens. The MCP expands tokenized IDs in resource_id and IDs embedded in fields before the backend call, then tokenizes the response again.

Apply means apply to the forked model. It does not write infrastructure, call an AWS mutation API, or guarantee application connectivity.

Based on the Emfirge MCP and engine source.View source
Documentation