Volcengine Agent Identity

ReviewAudited by ClawScan on May 10, 2026.

Overview

This is a coherent identity/credential-management skill, but it handles login tokens, hosted credentials, environment bindings, and tool approvals, so users should install it only if they trust the underlying plugin.

This skill appears purpose-aligned, but it is sensitive: it can help manage login sessions, TIP tokens, OAuth/API-key credentials, and env-var credential bindings. Before installing, verify the underlying agent-identity plugin is trusted, keep approval actions human-only, use minimal scopes, and review stored credentials and bindings regularly.

Findings (5)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

The skill may help the agent access or manage credentials connected to the user's accounts.

Why it was flagged

The skill is explicitly intended to handle user login, workload tokens, OAuth credentials, and API keys. This is expected for the identity purpose, but it is high-impact account/credential authority.

Skill content
UserPool OIDC login ... TIP token ... credential hosting (出站授权 OAuth2, API key)
Recommendation

Use only with a trusted agent-identity plugin, approve only necessary providers/scopes, and periodically review or revoke stored credentials.

What this means

A credential bound into an environment variable could be used by other tools that run under the agent.

Why it was flagged

The skill can add credentials and bind them into environment variables for tools. This is purpose-aligned, but users should notice because it can make credentials available to later tool calls.

Skill content
`identity_fetch` ... `redirectUrl?`, `scopes?` | Add credential ... `identity_set_binding` ... Bind provider → env var for tool injection
Recommendation

Confirm the provider, scopes, redirect URL, and env var name before adding or binding credentials; prefer least-privilege credentials.

What this means

If approval controls were misconfigured outside this skill, risky shell/file actions could be approved too easily.

Why it was flagged

The artifacts document a tool that can approve high-risk actions, but also clearly state that approval must be user-initiated and the agent must not self-approve.

Skill content
`identity_approve_tool` ... Approve a high-risk tool call ... agent must never call `identity_approve_tool`
Recommendation

Keep approval as a human-only action and verify the platform enforces that the agent cannot call the approval tool autonomously.

What this means

Commands or file paths submitted for risk analysis may be included in an LLM evaluation context.

Why it was flagged

Optional LLM risk checking may send command or path context to an LLM for classification. This is disclosed and purpose-aligned, but it is a provider data-flow users should understand.

Skill content
LLM-based (optional): When rules return "medium", an LLM re-evaluates for context
Recommendation

Enable LLM-based risk checking only if acceptable for your privacy needs, and avoid including secrets in commands or file paths.

What this means

Users cannot verify the plugin implementation from this skill package alone.

Why it was flagged

The provided artifact contains only instructions and does not include the implementation of the underlying agent-identity plugin, so code/provenance review is limited.

Skill content
Source: unknown; Homepage: none; No install spec — this is an instruction-only skill.
Recommendation

Verify the installed agent-identity plugin and configuration come from a trusted Volcengine/OpenClaw source before enabling credential management.