- Harness on employee device
- Cloud-hosted agent
The path of a tool call
- Prompt. The employee asks the agent to pull a customer record from Salesforce and post it in Slack.
- Request. The agent sends the prompt to the model, directly or through your LLM router.
- Suggested tool call. The model replies with a tool to run, here Salesforce’s
get_record. - Check the call. Before the tool runs, the hook’s
PreToolUseevent sends the tool name and arguments to Lumos. - Allow or deny. Lumos checks your policies against the call and the person’s identity, such as groups, team, and title. A denied call stops here, and Lumos logs it as denied.
- Allowed call. The tool runs on an external MCP server, directly or through your MCP gateway, or locally, like Bash or a local MCP server.
- Result. The output returns to the agent.
- Log the outcome. After the tool runs, the hook’s
PostToolUseevent reports the completed call to Lumos, which logs it. - Response. The employee sees the answer.
Rollout
- Your MDM pushes the hook config (Jamf, Intune, or Kandji) as managed settings employees can’t edit or remove. No Lumos software is installed.
- Each device enrolls once and gets a device token. Lumos attributes every call to the person your device inventory assigns that device to.
- For a trial, one command installs the hooks in a user’s own settings, without an MDM.
LLM routers and MCP gateways
Both stay in place. Lumos adds per-person policy and a log of every call.- LLM routers change where inference goes, not where tools run, so the hook works the same.
- MCP gateways see a call only after Lumos allows it. Built-in tools and local MCP servers never pass through a gateway, and the hook still covers them.
Verdicts and timing
- Allow is silent. The agent’s own permission prompts still apply.
- Deny stops the call and names the policy: Blocked by your organization’s Lumos policy “<name>”, followed by the policy’s description if it has one.
- Checks time out after 4 seconds. The call proceeds. If Lumos received the call but could not evaluate it in time, Lumos logs it as not evaluated. If the hook could not reach Lumos at all, it is not logged.
- With the Claude plugin, each request waits at most 4 seconds and the hook spends at most 8 seconds in all. If Lumos cannot answer in time, the call proceeds and nothing is logged. A refusal from Lumos blocks the call with a reason code; see the Claude plugin.
- Unenrolled or revoked devices are denied.
- Policy edits apply within seconds. Identity changes, such as a group removal, apply within 5 minutes.