Safety and model limits
Keep cloud access read-only and use branches to inspect modeled consequences through the documented lenses.
Read-only AWS access
Emfirge collects infrastructure through an IAM role assumed with AWS STS. Review the CloudFormation template and its trust policy before connecting your account. The analysis and mutation tools do not apply changes to real AWS resources.
The setup flow creates an IAM role in your account. You approve that setup in AWS; subsequent proposed infrastructure changes stay in Emfirge’s model.
Advisory by design
A block verdict is an analysis result. Emfirge does not physically prevent an agent, user, or pipeline with separate AWS credentials from deploying. Any approval policy must be enforced by your own workflow.
Privacy and data flow
The local MCP server sends requests to the configured Emfirge backend. The backend collects and processes infrastructure information. Strict privacy mode tokenizes supported identifiers in covered tool responses before they reach the host model; it does not mean infrastructure stays only on your computer.
The checked-in branch handlers return backend JSON directly and do not apply the same tokenization wrapper used by scan and findings tools. Do not assume strict mode redacts every branch response.
Treat local token mappings and analysis output as sensitive infrastructure data. Review the client and backend behavior for the tools you use.
Coverage and uncertainty
Graph confidence and coverage depend on collected fields, modeled relationships, and the checks that ran. A model cannot establish application behavior or complete runtime reachability.
Prefer a precise limitation over an unsupported promise. Review scanner availability and unknown cost notes before taking action.
Revoke AWS access
Remove the CloudFormation stack that created the read-only role to revoke that role’s access. Removing the MCP client configuration alone does not remove the IAM role or stored scan data.