manage-users — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited manage-users (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Manage users, user groups, and service accounts via MCP.
Call MCP tool: harness_list
Parameters:
resource_type: "user"
search_term: "<name or email>"Users are account-scoped. Use search_term to filter by name or email.
Call MCP tool: harness_get
Parameters:
resource_type: "user"
resource_id: "<user_id>"List groups:
Call MCP tool: harness_list
Parameters:
resource_type: "user_group"
org_id: "<organization>"
project_id: "<project>"
search_term: "<group name>"Get group details:
Call MCP tool: harness_get
Parameters:
resource_type: "user_group"
resource_id: "<group_identifier>"
org_id: "<organization>"
project_id: "<project>"Create a group:
Call MCP tool: harness_create
Parameters:
resource_type: "user_group"
org_id: "<organization>"
project_id: "<project>"
body:
identifier: "backend_team"
name: "Backend Team"
description: "Backend engineering team"
users:
- "<user_id_1>"
- "<user_id_2>"Delete a group:
Call MCP tool: harness_delete
Parameters:
resource_type: "user_group"
resource_id: "<group_identifier>"
org_id: "<organization>"
project_id: "<project>"List service accounts:
Call MCP tool: harness_list
Parameters:
resource_type: "service_account"
org_id: "<organization>"
project_id: "<project>"Create a service account:
Call MCP tool: harness_create
Parameters:
resource_type: "service_account"
org_id: "<organization>"
project_id: "<project>"
body:
identifier: "ci_bot"
name: "CI Bot"
description: "Service account for CI pipeline automation"
email: "[email protected]"Delete a service account:
Call MCP tool: harness_delete
Parameters:
resource_type: "service_account"
resource_id: "<service_account_identifier>"
org_id: "<organization>"
project_id: "<project>"Call MCP tool: harness_list
Parameters:
resource_type: "permission"This returns all platform permissions. Use this to understand what permissions can be assigned via roles.
| Resource Type | Scope | Operations | Description |
|---|---|---|---|
user | Account | list, get | Platform users (read-only) |
user_group | Project | list, get, create, delete | User groups for RBAC |
service_account | Project | list, get, create, delete | API automation accounts |
permission | Account | list | Available permissions (read-only) |
This skill manages principals (users, groups, service accounts). Use /manage-roles to assign roles and resource groups to these principals:
/manage-users -- Create the user group or service account/manage-roles -- Assign a role + resource group to that principal/manage-roles to assign a role to the service account~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.