Enumerate logged on users
AI agents call inject_net_logons to retrieve information from Cobalt Strike MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about currently logged-on users on a target system, which is a reconnaissance/read operation. However, severity is elevated to 'medium' rather than 'low' because: (1) it operates within the Cobalt Strike red team framework, indicating adversarial context; (2) enumeration of active user sessions is valuable reconnaissance for lateral movement, privilege escalation, and targeting…
From the tool's definition Tool name 'inject_net_logons' with description 'Enumerate logged on users' performs information discovery without modifying system state. The 'enumerate' operation is a read-only query for user session data.
Attacks that exploit this kind of access
Enumerate logged on users. It is categorised as a Read tool in the Cobalt Strike MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for inject_net_logons: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Cobalt Strike MCP Server. Nothing to install.
inject_net_logons is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the inject_net_logons rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for inject_net_logons. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
inject_net_logons is provided by the Cobalt Strike MCP Server MCP server (mickeydb/cobalt-strike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →