Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md - `SKILL.md` keeps scenario routing and confirmation policy.
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed Gate unified-account helper with financial write capability, but its artifacts consistently require user confirmation before changes.
Install only if you intend to let the assistant manage Gate unified-account workflows through your local MCP setup. Use API keys limited to the stated Unified permissions, review every Action Draft carefully, and do not confirm borrowing, repayment, leverage, mode, or collateral changes unless the amount and account scope are exactly what you want.
Referenced artifact was not completely inspected
- `SKILL.md` keeps scenario routing and confirmation policy.
The README mandates fixed Chinese labels for unified-mode values and a Chinese warning message, but does not offer a language choice or document a justified locale restriction. This can violate language/locale policy because the skill forces a specific language in responses regardless of user preference.
The trigger phrases are broad enough to activate this skill on loosely related prompts such as general account-mode, leverage, or transfer questions without strong scoping. In a skill that can perform financial mutations like borrowing, repayment, leverage changes, and collateral toggles, over-broad routing increases the chance the wrong skill is selected and a user query is interpreted in a higher-risk operational context than intended.
Skill grants unrestricted tool access without appropriate constraints. An agent with unfettered tool access can perform arbitrary actions including file modification, network requests, and code execution.
## General Rules
⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding.
Do NOT select or call any tool until all rules are read. These rules have the highest priority.
→ Read `./references/gate-runtime-rules.md`
- **Only call MCP tools explicitly listed in this skill.** Tools not documented here must NOT be called, even if they
exist in the MCP server.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- Credentials Source: Local Gate MCP deployment (`GATE_API_KEY`, `GATE_API_SECRET`)
- API Key Required: Yes
- Permissions: Unified:Read, Unified:Write
- Never ask the user to paste secrets into chat; rely on the configured MCP session only.
- API Key Provisioning Reference: https://www.gate.com/myaccount/profile/api-key/manage (create or rotate keys outside the chat when the local MCP setup requires them).
### Installation Check
The response rules require unified mode display labels to use Chinese text and prescribe a fixed Chinese warning string when unified accounts are not enabled. This forces a specific language output without user opt-in or an explicit language-selection mechanism, which is a natural-language policy violation.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
## 1. MCP Session and Authentication
- Use the already configured Gate MCP session for the current host.
- Local Gate MCP deployments use `GATE_API_KEY` and `GATE_API_SECRET`; never ask the user to paste these secrets into chat.
- Minimal permissions for this skill are `Unified:Read` and `Unified:Write`.
- If the required Gate MCP tools are missing, stop write actions and switch to setup guidance only.
- If the MCP session returns an auth or permission error, stop write actions and guide the user to repair the configured local MCP credentials before continuing.
The document requires mode labels to map strictly to Chinese strings and also mandates a Chinese top warning message. This imposes a specific language/locale on all outputs without any user opt-in or documented regional justification, which matches the language-policy violation criteria.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
3. Calculate impact note and build `Mode Switch Draft`.
4. After explicit confirmation, execute via `set_unified_mode` and output `Mode Switch Result Report`.
**Unexpected Behavior**:
1. Executes mode switch without confirmation.
2. Ignores current mode and submits redundant or wrong target mode.
3. Returns success without showing resulting mode.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
3. Calculate impact note and build `Mode Switch Draft`.
4. After explicit confirmation, execute via `set_unified_mode` and output `Mode Switch Result Report`.
**Unexpected Behavior**:
1. Executes mode switch without confirmation.
2. Ignores current mode and submits redundant or wrong target mode.
3. Returns success without showing resulting mode.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
3. Calculate impact note and build `Mode Switch Draft`.
4. After explicit confirmation, execute via `set_unified_mode` and output `Mode Switch Result Report`.
**Unexpected Behavior**:
1. Executes mode switch without confirmation.
2. Ignores current mode and submits redundant or wrong target mode.
3. Returns success without showing resulting mode.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
3. Calculate impact note and build `Mode Switch Draft`.
4. After explicit confirmation, execute via `set_unified_mode` and output `Mode Switch Result Report`.
**Unexpected Behavior**:
1. Executes mode switch without confirmation.
2. Ignores current mode and submits redundant or wrong target mode.
3. Returns success without showing resulting mode.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
3. Calculate impact note and build `Mode Switch Draft`.
4. After explicit confirmation, execute via `set_unified_mode` and output `Mode Switch Result Report`.
**Unexpected Behavior**:
1. Executes mode switch without confirmation.
2. Ignores current mode and submits redundant or wrong target mode.
3. Returns success without showing resulting mode.