best-practices
Warn
Audited by Runlayer on Mar 11, 2026
Risk Level: MEDIUM
Scan Summary
Flagged Files (2)
best-practices/jit-user-context.mdMEDIUM
80.8%
Risky tool definition detected
## Loading Additional Profile Fields To also provision `department` or `displayName`, add more `SetVariable` nodes after the connector call: ```yaml - kind: SetVariable id: setDepartment_REPLACE3 variable: Global.UserDepartment value: =If(IsBlank(Topic.M365Profile.department), "Unknown", Topic.M365Profile.department) ``` Create a corresponding `UserDepartment.mcs.yml` global variable for each additional field, using `aIVisibility: UseInAIContext` if the orchestrator should reason about it. ## Av
Prompt Injection
best-practices/orchestrator-variables.mdLOW
55.3%
Tool passed security scan
Passed Files (2)Click to expand
best-practices/jit-glossary.mdOK
49.5%
Tool passed security scan
best-practices/SKILL.mdOK
35.8%
Tool passed security scan
Audit Metadata