This record as markdown: /tools/0xyg3n-claude-c2/local-users.md
What local_users does on Claude C2
AI agents call local_users to retrieve information from Claude C2 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why local_users is rated Low
This is a read-only operation that enumerates system user and group accounts. While it retrieves sensitive system information (user account enumeration) that could enable privilege escalation or lateral movement planning, the tool itself performs no destructive, write, or execute operations.
From the tool's definition Tool name is 'local_users' and description states 'List local users/groups' — it retrieves and queries user/group information without modifying or deleting data.
Attacks that exploit this kind of access
The rule that runs local_users safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude C2, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For local_users, this is the rule to start with:
local_users is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude C2, apply this rule, and every local_users call is checked against it from then on.
Questions about local_users
List local users/groups. Auto-selects client. It is categorised as a Read tool in the Claude C2 MCP Server, which means it retrieves data without modifying state.
Register the Claude C2 MCP server in PolicyLayer and add a rule for local_users: 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 Claude C2. Nothing to install.
local_users 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 local_users 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 local_users. 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.
local_users is provided by the Claude C2 MCP server (0xyg3n/claude-c2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude C2, and thousands of servers like it.
This server
Across the catalogue