Reading a Secret Is an Operator Action, and Findings Belong to Who Recorded Them ​

October 19, 2026 · InfraScout Team

InfraScout's role model follows least privilege in two places worth knowing about. Tools that return a credential take an operator role, even though they change nothing. And a standard user can change only the findings they recorded themselves.

Credentials need operator authority ​

Most read-only tools tell you about your environment. A few hand you the keys to it: mscloud_security_get_laps_credential returns a device's local administrator password, mscloud_security_get_bitlocker_key returns a recovery key, and include_secret_values on mscloud_platform_get_resource returns Azure Automation variable and connection values.

InfraScout treats reading a secret as an operator action. These require an Admin, Operator, or MCPOperator role, or an agentic workflow:

  • The two getters are not offered to read-only roles, in chat or from a connected MCP client.
  • mscloud_platform_get_resource stays available to everyone. Only include_secret_values needs an operator role, and without it the same call returns placeholders.
  • A read-only Task Agent cannot read secrets, even when an operator started it.

The list tools are open to every role. mscloud_security_list_laps_credentials and mscloud_security_list_bitlocker_keys show which devices have a managed password or a stored recovery key, which is what most assessments need, and they never return the secret itself.

If you hold a standard role and need a key to unlock a drive or sign in locally, ask an operator. The list tools' descriptions say that retrieving the secret takes an operator role, so the AI can tell you that up front.

Findings belong to who recorded them ​

Every finding records who created it, and that record decides who can change it. Through the insight tools, in chat or from a connected MCP client, Users and MCPUser callers can update the status of, delete, or overwrite with insight_save only the findings they recorded themselves. Admin, Operator, and MCPOperator callers can change any finding they can see.

Findings with no recorded author, such as those saved before InfraScout began recording authorship, can be changed only by an operator.

When a change is refused, the message says why: another user recorded the finding, or it has no recorded author. It also says that an operator can make the change. The AI can tell you who to ask, instead of reporting that a finding you can see is missing. Saving a new finding, and reading, listing, and aggregating findings, work for every role as before.

Admins can read any execution from chat ​

session_get_execution follows the same rule in chat as in the portal. Admins can open any execution's stored output from a conversation, and other roles read the executions that ran on their behalf.

See Tool Annotations and Role Scoping for how the role tiers apply, Insight Tools for the ownership rule, and the BitLocker and LAPS tools for the per-tool reference.

Questions or feedback? Reach us at info@infrascout.cloud.