lfx-mcp: Skill for Claude Code

Escalation guidelines (lfx-mcp)

These detail the boundaries behind the escalation decision: the gateway's critical parts, its shared surfaces, and what scale-with-importance means here. A change escalates to needs-human if it has that character, wherever in the tree it lives; one that merely sits near such an area without moving it does not. Match the substance, not the neighborhood. Each guideline describes a boundary, not a list of files: the paths and examples are illustrative anchors, never an exhaustive inventory, and the list itself is a floor, not a ceiling. A change that endangers what these guidelines protect without matching any single item still needs a human, and if the code seems to have drifted from how this file describes it, that drift is itself a reason to escalate.

lfx-mcp is an authenticated authorization gateway in front of production LFX data, and ARCHITECTURE.md is the authoritative description of how it works. Two of its properties shape everything below. First, a caller's tools are decided once, at registration time, from the token it presents; for most tools nothing is checked again afterwards. Second, upstream APIs split into two classes: those where the LFX platform authorizes the caller natively, and those where this server is the only authorization layer.

The test

Whatever the change touches, escalate only when you can point to the specific load-bearing thing it alters and say what now behaves differently: what it means for a request to be authenticated, a tool's required access level, whether a brokered tool still checks access before it proxies, which write tools are exposed, an upstream payload type the tools marshal, or what credential or personal data can leave the server. Establish it from the diff (base versus head), not from the area the diff lives in. Three corollaries follow, and they account for most false alarms: