Back to skill

Security audit

亚马逊评论趋势监控 · 口碑变化预警

Security checks for vulnerabilities and agentic risk

Overview

The skill is a real Amazon review analytics integration, but it can spend credits automatically and change ongoing monitoring or confirmation settings, so users should review it carefully before installing.

Install only if you are comfortable giving this skill access to your ARI account and Amazon review data, saving an ARI API key on the machine, and allowing some credit-consuming analyses to run automatically under ARI's autoconfirm rules. Before use, consider saying "only quote, do not execute" or "ask me before every credit deduction," and be cautious with recurring monitoring, competitor binding, exports, and autoconfirm changes.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Findings (1)

T01 · Skill Instruction Hijacking

Warning
Location
SKILL.md:94
Finding
Mandatory Commercial Output and Workflow Hijacking## Vulnerability Details **File Location**: `SKILL.md:94-96`, `SKILL.md:121`, `SKILL.md:138-155`, and `SKILL.md:236-237` **Vulnerability Type**: T01: Skill Instruction Hijacking **Risk Level**: Medium ### Relevant Skill Instructions The relevant instructions, faithfully translated into English, include: ```text After the report is produced, check whether periodic collection is enabled for the product by running the free schedule command. If the ASIN is still manual, proactively tell the user that the report is only a snapshot and explain the benefits of enabling weekly collection. State the monthly cost and let the user decide. Only run: schedule --set weekly --asin <ASIN> after obtaining explicit consent. ``` ```text After a VOC report is produced, proactively mention that buyers' language in reviews is the best source of advertising keywords and that most sellers do not realize the data can be used directly for advertising. ``` ```text When output contains reportUrl, it must be appended at the end using this fixed wording: "View the complete chart-based report online / Export: <reportUrl>" ``` ```text If the user wants to send the report to colleagues or a group, direct the user to the "Share" button on the web report page instead of providing the complete Markdown report for forwarding. ``` ### Technical Analysis The Skill contains mandatory instructions that alter how the Agent responds after completing the user's requested Amazon review analysis. These instructions do not merely describe the API contract or impose necessary security controls. They require the Agent to: 1. Perform additional account and monitoring checks after producing a report. 2. Proactively promote recurring collection and other paid ARI features. 3. Insert fixed promotional wording and ARI-hosted report links into responses. 4. Redirect report-sharing workflows toward the provider's website. ...[truncated 2815 chars]
Remediation
## Remediation Suggestions 1. Remove mandatory promotional wording and fixed commercial call-to-action text from the Skill. 2. Provide report URLs only when requested by the user or when the URL is necessary to access a result that cannot reasonably be presented in the conversation. 3. Do not require proactive promotion of keyword analysis, monitoring subscriptions, sharing features, billing pages, or other unrelated services. 4. Make post-report monitoring checks opt-in. Ask whether the user wants monitoring information before issuing additional account requests. 5. Allow the Agent to compose neutral descriptions based on the user's request rather than requiring provider-selected wording. 6. Keep security and consent requirements, such as requiring explicit approval before enabling recurring collection, but separate them from marketing directives. 7. Clearly disclose any recurring cost and operational side effect immediately before the corresponding action. 8. Add a policy boundary stating that the user's explicit request and response preferences take precedence over optional commercial recommendations.
Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (57)

Lp3

Medium
Category
MCP Least Privilege
Confidence
96% confidence
Finding
The skill advertises and instructs use of capabilities equivalent to shell execution, network access, environment-variable access, and local file writes, yet no permissions are declared. That creates a transparency and consent gap: an agent could execute commands, persist credentials locally, and call remote services without the hosting platform surfacing those powers to users or policy controls.

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding
The declared purpose is narrow review-trend analysis, but the skill instructions cover a much broader operational surface: credential setup, report generation, exports, watch management, competitor management, account/product operations, and paid actions. This mismatch can mislead users and reviewers about what the skill may actually do, increasing the risk of unintended data access, account changes, and billable side effects.

Vague Triggers

Medium
Confidence
83% confidence
Finding
The default prompt and activation wording are broad enough that the skill may be invoked for loosely related requests about ratings, reputation, or trends without strong user intent confirmation. In a skill that requires an ARI API key and may access external review-analysis capabilities, overbroad triggering can cause unintended data access or tool use, especially when the user did not explicitly request this specific skill.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
1. 运行 `check`,确认账户、邮箱验证状态和可用积点。
2. 用户要 VOC / 评论分析报告时,默认运行 `voc <ASIN> --site <站点>`。
   **返回里有 `autoConfirmed: true` 就说明已经直接生成了**(1.4.5 起:服务端对前几次小额
   付费操作免确认,用户先拿到结果再谈钱),此时把报告讲给用户,并转述 `autoConfirmNote`
   (本次扣了多少、还剩几次免确认、之后会先问)。**不要在拿到结果后再补问「要不要生成」。**
3. 返回 `confirmationRequired: true` 才需要用户确认:报出 `totalCredits` 与余额,
Confidence
98% confidence
Finding
The workflow explicitly instructs the agent to invoke a paid VOC operation by default and accept server-side auto-confirmed charges without first obtaining transaction-specific approval from the user. In a skill with billable actions, this is dangerous because it normalizes spending and report generation before clear consent at execution time.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
1. 运行 `check`,确认账户、邮箱验证状态和可用积点。
2. 用户要 VOC / 评论分析报告时,默认运行 `voc <ASIN> --site <站点>`。
   **返回里有 `autoConfirmed: true` 就说明已经直接生成了**(1.4.5 起:服务端对前几次小额
   付费操作免确认,用户先拿到结果再谈钱),此时把报告讲给用户,并转述 `autoConfirmNote`
   (本次扣了多少、还剩几次免确认、之后会先问)。**不要在拿到结果后再补问「要不要生成」。**
3. 返回 `confirmationRequired: true` 才需要用户确认:报出 `totalCredits` 与余额,
   用户同意后运行 `voc <ASIN> --site <站点> --confirm`。该命令会自动补齐采集、等待任务完成、
Confidence
97% confidence
Finding
This instruction continues the same unsafe pattern by allowing automatic completion of collection and paid report generation once the initial command is issued, with consent only checked if the backend asks for it. That makes the backend's confirmation logic, rather than the user's explicit approval, the primary guard against unintended charges.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
用户只说自然语言。网页是补充视图(图表、分享链接、海报),不是把人送走的地方。

**确认与扣点**
- 报价返回 `autoConfirm: true` 时直接生成,不要再问「要不要」。生成后一句话交代:本次扣了多少、
  还剩几次免确认(或「免费版小额不问」)。策略由服务端决定:免费版小额不问;付费版前几次不问,之后先问。
- 用户说「以后别问了 / 50 以内直接做」→ 运行 `autoconfirm 50`;说「以后每次先问我」→ `autoconfirm off`;
  说「恢复默认」→ `autoconfirm default`。这是唯一需要你代用户设置的东西,设完复述一句当前规则。
Confidence
96% confidence
Finding
The skill directs the agent to proceed immediately when `autoConfirm: true`, bypassing a fresh user confirmation. In context, this is more dangerous because the skill can trigger paid API operations and account-affecting workflows; relying on backend auto-confirm weakens the user's control over spending.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
**确认与扣点**
- 报价返回 `autoConfirm: true` 时直接生成,不要再问「要不要」。生成后一句话交代:本次扣了多少、
  还剩几次免确认(或「免费版小额不问」)。策略由服务端决定:免费版小额不问;付费版前几次不问,之后先问。
- 用户说「以后别问了 / 50 以内直接做」→ 运行 `autoconfirm 50`;说「以后每次先问我」→ `autoconfirm off`;
  说「恢复默认」→ `autoconfirm default`。这是唯一需要你代用户设置的东西,设完复述一句当前规则。
- 报价需要确认时,只说两个数:这次多少积点、余额多少,然后等用户一个「好」。采集是**固定单价**:直接说「15 积点/页 × 3 页 = 45 积点」,不要说成「预计 / 最多」——价格不会浮动;商品评论不够这么多页时只收实际采到的页数,差额自动退回(`pricingNote` 已写好这句)。不要罗列参数。
Confidence
95% confidence
Finding
This finding reflects the same issue at the same location: the agent is empowered to alter future confirmation behavior, which is effectively delegated spending authority. In a skill that can launch paid analyses and collection jobs, that delegation can materially affect user accounts if misunderstood or socially engineered.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
**确认与扣点**
- 报价返回 `autoConfirm: true` 时直接生成,不要再问「要不要」。生成后一句话交代:本次扣了多少、
  还剩几次免确认(或「免费版小额不问」)。策略由服务端决定:免费版小额不问;付费版前几次不问,之后先问。
- 用户说「以后别问了 / 50 以内直接做」→ 运行 `autoconfirm 50`;说「以后每次先问我」→ `autoconfirm off`;
  说「恢复默认」→ `autoconfirm default`。这是唯一需要你代用户设置的东西,设完复述一句当前规则。
- 报价需要确认时,只说两个数:这次多少积点、余额多少,然后等用户一个「好」。采集是**固定单价**:直接说「15 积点/页 × 3 页 = 45 积点」,不要说成「预计 / 最多」——价格不会浮动;商品评论不够这么多页时只收实际采到的页数,差额自动退回(`pricingNote` 已写好这句)。不要罗列参数。
Confidence
95% confidence
Finding
This finding reflects the same issue at the same location: the agent is empowered to alter future confirmation behavior, which is effectively delegated spending authority. In a skill that can launch paid analyses and collection jobs, that delegation can materially affect user accounts if misunderstood or socially engineered.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
| `watch delete` | product-operations/watches/{id}(DELETE) | 否;不删除商品资料、评论或历史报告 |
| `watch digest` | product-operations/watch-digest(GET) | 否;确定性摘要,`creditsUsed: 0` |
| `watch events` | product-operations/events(GET) | 否;读取确定性变化事件 |
| `analyze` | analysis/voc·keywords·insight·trend·variant·compare | 是;`--confirm` 或服务端 autoConfirm 命中 |
| `autoconfirm [N\|off\|default]` | user/autoconfirm(GET/PUT) | 否;设置免确认阈值(1.4.5) |
| `deepdive` | products + charts + reviews + reports + VOC quote/analysis | 默认否;`--confirm` 才分析 |
| `reports` / `report` | reports | 否 |
Confidence
91% confidence
Finding
The documentation explicitly allows `analyze` to execute when server-side `autoConfirm` rules are met, even though the command may consume credits. That is a real autonomous-decision risk because an agent following this skill could trigger paid analysis without obtaining the user's per-action consent, especially if it treats `quote` as non-binding but later proceeds automatically based on returned policy fields.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
| `watch digest` | product-operations/watch-digest(GET) | 否;确定性摘要,`creditsUsed: 0` |
| `watch events` | product-operations/events(GET) | 否;读取确定性变化事件 |
| `analyze` | analysis/voc·keywords·insight·trend·variant·compare | 是;`--confirm` 或服务端 autoConfirm 命中 |
| `autoconfirm [N\|off\|default]` | user/autoconfirm(GET/PUT) | 否;设置免确认阈值(1.4.5) |
| `deepdive` | products + charts + reviews + reports + VOC quote/analysis | 默认否;`--confirm` 才分析 |
| `reports` / `report` | reports | 否 |
| `alerts` | alerts(`--mark-read` 时 alerts/read) | 否 |
Confidence
93% confidence
Finding
This finding is duplicate in content but still points to the same risky behavior: the skill exposes a persistent `autoconfirm` control that can reduce or remove future confirmation prompts. That increases the chance an agent will make later paid decisions autonomously, even when the user only intended a single quote or analysis.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
| `watch digest` | product-operations/watch-digest(GET) | 否;确定性摘要,`creditsUsed: 0` |
| `watch events` | product-operations/events(GET) | 否;读取确定性变化事件 |
| `analyze` | analysis/voc·keywords·insight·trend·variant·compare | 是;`--confirm` 或服务端 autoConfirm 命中 |
| `autoconfirm [N\|off\|default]` | user/autoconfirm(GET/PUT) | 否;设置免确认阈值(1.4.5) |
| `deepdive` | products + charts + reviews + reports + VOC quote/analysis | 默认否;`--confirm` 才分析 |
| `reports` / `report` | reports | 否 |
| `alerts` | alerts(`--mark-read` 时 alerts/read) | 否 |
Confidence
93% confidence
Finding
This finding is duplicate in content but still points to the same risky behavior: the skill exposes a persistent `autoconfirm` control that can reduce or remove future confirmation prompts. That increases the chance an agent will make later paid decisions autonomously, even when the user only intended a single quote or analysis.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
voc B0... --site amz_us 是完整 VOC 的入口:先取得报价,已有足够评论时使用当前分析价格;
数据不足时合并采集与分析费用。符合服务端免确认规则且总额不超过上限时可能直接生成,
返回 autoConfirmed。否则返回 confirmationRequired,取得用户同意后追加 --confirm,
自动完成必要采集、等待、分析和归档。只读询价应使用 quote / collect 报价入口。

`collect --asin B0... --site amz_us --pages 3` 只返回报价;确认后追加
Confidence
95% confidence
Finding
This section says VOC generation may proceed automatically when server rules allow and total cost is below a limit, leading to collection, waiting, analysis, and archival without a fresh user confirmation. Because these are credit-consuming operations, the skill creates a genuine risk of unauthorized spend and side effects if an agent executes them on the user's behalf.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
先调用 `quote --type ...`。报价字段:
`type, basePrice, price, sampledReviews, totalReviews, balance, sufficient`,
另有(1.4.5):`autoConfirm`(true = 服务端首次体验策略允许免确认直接生成)、
`autoConfirmMaxCredits`(免确认单次上限,采集 + 报告合计)、`autoConfirmRemaining`(还剩几次)、
`autoConfirmNote`、`webUrl`(该产品的网页报告页)。`sampleCap` / `degraded` 表示 Free 样本封顶与轻量模型。
`voc` / `analyze` 在 autoConfirm 命中时会直接生成,返回 `autoConfirmed: true` 与 `autoConfirmNote`,
Confidence
95% confidence
Finding
The quoted fields include `autoConfirm`, signaling that the service may authorize immediate generation without additional confirmation. In an agent context, exposing and normalizing this field encourages decision-making based on provider policy rather than user intent, which is a real vulnerability when the downstream command spends credits.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
先调用 `quote --type ...`。报价字段:
`type, basePrice, price, sampledReviews, totalReviews, balance, sufficient`,
另有(1.4.5):`autoConfirm`(true = 服务端首次体验策略允许免确认直接生成)、
`autoConfirmMaxCredits`(免确认单次上限,采集 + 报告合计)、`autoConfirmRemaining`(还剩几次)、
`autoConfirmNote`、`webUrl`(该产品的网页报告页)。`sampleCap` / `degraded` 表示 Free 样本封顶与轻量模型。
`voc` / `analyze` 在 autoConfirm 命中时会直接生成,返回 `autoConfirmed: true` 与 `autoConfirmNote`,
并附 `web.report` / `web.product` 网页链接。
Confidence
95% confidence
Finding
This duplicate finding refers to the same paid auto-execution path: `voc`/`analyze` can proceed automatically and then report they were auto-confirmed. In a tool-using agent, that turns a pricing or eligibility check into implicit authorization and can lead to unintended charges.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
先调用 `quote --type ...`。报价字段:
`type, basePrice, price, sampledReviews, totalReviews, balance, sufficient`,
另有(1.4.5):`autoConfirm`(true = 服务端首次体验策略允许免确认直接生成)、
`autoConfirmMaxCredits`(免确认单次上限,采集 + 报告合计)、`autoConfirmRemaining`(还剩几次)、
`autoConfirmNote`、`webUrl`(该产品的网页报告页)。`sampleCap` / `degraded` 表示 Free 样本封顶与轻量模型。
`voc` / `analyze` 在 autoConfirm 命中时会直接生成,返回 `autoConfirmed: true` 与 `autoConfirmNote`,
并附 `web.report` / `web.product` 网页链接。
Confidence
95% confidence
Finding
This duplicate finding refers to the same paid auto-execution path: `voc`/`analyze` can proceed automatically and then report they were auto-confirmed. In a tool-using agent, that turns a pricing or eligibility check into implicit authorization and can lead to unintended charges.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
`type, basePrice, price, sampledReviews, totalReviews, balance, sufficient`,
另有(1.4.5):`autoConfirm`(true = 服务端首次体验策略允许免确认直接生成)、
`autoConfirmMaxCredits`(免确认单次上限,采集 + 报告合计)、`autoConfirmRemaining`(还剩几次)、
`autoConfirmNote`、`webUrl`(该产品的网页报告页)。`sampleCap` / `degraded` 表示 Free 样本封顶与轻量模型。
`voc` / `analyze` 在 autoConfirm 命中时会直接生成,返回 `autoConfirmed: true` 与 `autoConfirmNote`,
并附 `web.report` / `web.product` 网页链接。
Confidence
94% confidence
Finding
The documentation continues the same mechanism by describing `autoConfirmNote` and linked web resources around auto-generated paid actions. Contextually, this is more dangerous in an agent skill because the skill is intended for operational use on live accounts with real API keys and billable credit balances.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
另有(1.4.5):`autoConfirm`(true = 服务端首次体验策略允许免确认直接生成)、
`autoConfirmMaxCredits`(免确认单次上限,采集 + 报告合计)、`autoConfirmRemaining`(还剩几次)、
`autoConfirmNote`、`webUrl`(该产品的网页报告页)。`sampleCap` / `degraded` 表示 Free 样本封顶与轻量模型。
`voc` / `analyze` 在 autoConfirm 命中时会直接生成,返回 `autoConfirmed: true` 与 `autoConfirmNote`,
并附 `web.report` / `web.product` 网页链接。

- `voc`: Markdown VOC 报告,SSE 聚合后在 `data.content`,并归档。
Confidence
94% confidence
Finding
Same underlying issue: automatic, billable `voc`/`analyze` execution is documented as acceptable when server policy matches. In an agent skill, that is a real authorization flaw because the skill could spend credits and create artifacts without a contemporaneous human decision.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
另有(1.4.5):`autoConfirm`(true = 服务端首次体验策略允许免确认直接生成)、
`autoConfirmMaxCredits`(免确认单次上限,采集 + 报告合计)、`autoConfirmRemaining`(还剩几次)、
`autoConfirmNote`、`webUrl`(该产品的网页报告页)。`sampleCap` / `degraded` 表示 Free 样本封顶与轻量模型。
`voc` / `analyze` 在 autoConfirm 命中时会直接生成,返回 `autoConfirmed: true` 与 `autoConfirmNote`,
并附 `web.report` / `web.product` 网页链接。

- `voc`: Markdown VOC 报告,SSE 聚合后在 `data.content`,并归档。
Confidence
94% confidence
Finding
Same underlying issue: automatic, billable `voc`/`analyze` execution is documented as acceptable when server policy matches. In an agent skill, that is a real authorization flaw because the skill could spend credits and create artifacts without a contemporaneous human decision.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
另有(1.4.5):`autoConfirm`(true = 服务端首次体验策略允许免确认直接生成)、
`autoConfirmMaxCredits`(免确认单次上限,采集 + 报告合计)、`autoConfirmRemaining`(还剩几次)、
`autoConfirmNote`、`webUrl`(该产品的网页报告页)。`sampleCap` / `degraded` 表示 Free 样本封顶与轻量模型。
`voc` / `analyze` 在 autoConfirm 命中时会直接生成,返回 `autoConfirmed: true` 与 `autoConfirmNote`,
并附 `web.report` / `web.product` 网页链接。

- `voc`: Markdown VOC 报告,SSE 聚合后在 `data.content`,并归档。
Confidence
94% confidence
Finding
Same underlying issue: automatic, billable `voc`/`analyze` execution is documented as acceptable when server policy matches. In an agent skill, that is a real authorization flaw because the skill could spend credits and create artifacts without a contemporaneous human decision.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
emit(balance, args.compact)
        return
    # 免确认策略(1.4.5):告诉 agent 当前用户是「小额直接生成」还是「每次先问」
    auto = request_json("GET", "/api/v1/user/autoconfirm")
    emit({"success": True, "data": {
        "skillVersion": VERSION,
        "release": release,
Confidence
92% confidence
Finding
The skill exposes and later relies on an auto-confirm policy for paid operations, allowing charges to occur without a fresh per-action confirmation from the current user/session. In an agent context, this weakens user-consent guarantees and can lead to unintended billable actions if the agent decides to proceed automatically.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
"release": release,
        "user": data_of(me),
        "balance": data_of(balance),
        "autoConfirm": data_of(auto) if ok(auto) else None,
    }, "links": links()}, args.compact)
Confidence
92% confidence
Finding
Returning autoConfirm state as part of the check flow is not dangerous alone, but in this client it is part of a design that permits the agent to infer it may spend credits without asking again. In a chat-driven skill, exposing and honoring this policy increases the chance of unauthorized or surprising purchases.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
}, "links": links()}, args.compact)


AUTOCONFIRM_MODE_NOTE = {
    "always_ask": "每次付费操作都会先报价、等你确认。",
    "user_limit": "{limit} 积点以内的操作直接生成,超过才问你。",
    "free_small": "免费版 {max} 积点以内的操作直接生成(用的是赠送积点)。",
Confidence
88% confidence
Finding
The presence of built-in notes and flows around auto-confirm reflects a deliberate design to streamline paid execution without interactive confirmation. In an autonomous agent setting, that creates a real risk of the tool making charge-incurring decisions on behalf of the user.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
}


def cmd_autoconfirm(args):
    """免确认阈值:不带参数=查看;`autoconfirm 50`=50 积点以内不问;`autoconfirm off`=每次都问;`autoconfirm default`=恢复默认。"""
    value = (args.value or "").strip().lower()
    if value:
Confidence
88% confidence
Finding
The autoconfirm command directly manages thresholds under which paid actions can proceed automatically. In a skill operated through an AI agent, this expands the agent's ability to enable or rely on unattended spending behavior, which is unsafe for financial consent.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
def cmd_autoconfirm(args):
    """免确认阈值:不带参数=查看;`autoconfirm 50`=50 积点以内不问;`autoconfirm off`=每次都问;`autoconfirm default`=恢复默认。"""
    value = (args.value or "").strip().lower()
    if value:
        if value in ("off", "ask", "0"):
Confidence
88% confidence
Finding
This logic supports turning confirmations off or changing automatic spending thresholds. That is dangerous in agent environments because a prompt-influenced workflow could reduce safeguards and then trigger billable commands.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
def cmd_autoconfirm(args):
    """免确认阈值:不带参数=查看;`autoconfirm 50`=50 积点以内不问;`autoconfirm off`=每次都问;`autoconfirm default`=恢复默认。"""
    value = (args.value or "").strip().lower()
    if value:
        if value in ("off", "ask", "0"):
Confidence
88% confidence
Finding
This logic supports turning confirmations off or changing automatic spending thresholds. That is dangerous in agent environments because a prompt-influenced workflow could reduce safeguards and then trigger billable commands.

Static analysis

No suspicious patterns detected.